Hacker News Reader

> But microservices are also about coupling: just have a self-contained service that does one thing.

What stops you from creating a module inside a monolith with an interface that provides a self-contained service that does one thing?

View on HN

You can. But one day, some 10xer will be short on time and will duct tape your module with 10 other modules.

The newish argument for microservices is that they enable compositionality, so wouldn't that same hypothetical apply? I.e. some 10xer is short on time and glues a bunch of microservices together and now you have the same problem but worse because there's no IDE allowing you to trace the code?

You have a problem. You decide to use regular expressions to solve it. Now you have two problems.

You have a problem. You decide to use microservices to solve it. Now you have ten problems.

Reply on news.ycombinator.com