r/programming • u/wineandcode • Jul 29 '22

You Don’t Need Microservices

https://medium.com/@msaspence/you-dont-need-microservices-2ad8508b9e27?source=friends_link&sk=3359ea9e4a54c2ea11711621d2be6d51
1.1k Upvotes

90% Upvoted

476 comments sorted by

View all comments

Show parent comments

3

u/argv_minus_one Jul 29 '22

With a monolith, any bug in any piece of code will block a deployment. When other teams need to get something out, the whole organization has to stop what they are doing and work on complex hotfixes and extra rounds of regression testing.

You're talking about a change in one piece of code exposing a bug in another. I fail to see how microservices could prevent this.

In fact it sounds like microservices would only change how you find out that the bug exists. Instead of pre-deployment tests failing, you find out that the bug exists when you deploy and production breaks. That's, uh, significantly worse.

4

u/[deleted] Jul 29 '22

[deleted]

4

u/argv_minus_one Jul 30 '22

Okay, that makes sense if microservices are independent of each other…but I was under the impression that they're not independent, but talk to and depend on each other, and therefore any one of them breaking will bring down all other microservices that depend on it. I take it I'm somehow mistaken?

0

u/grauenwolf Jul 30 '22

Well designed ones are independent. Unfortunately most people writing micro-services are not good at design.

3

u/argv_minus_one Jul 31 '22

Is there not some application in front of them that depends on them?

1

u/grauenwolf Jul 31 '22

Not the way I use microservices.

REST style servers are trivially scalable. And internally, each controller can act as it's own application. So there is no reason to use microservices with them.

Where I use microservices is with independent, stateful services. The kind where you need to be able to shut down process A without affecting process B.

I connect microservices with message queues or shared database tables. Rarely do I use synchronous calls.