| > Scaling a monolith is almost always cheaper than migrating to microservices and scaling that. No - it depends on capacity needs and current architecture. > When you split it into microservices you are adding a bunch of infrastructure that did not need to exist. Unless you need to scale in an economical manner. > Your app performance will likely go way down since things that used to be function calls are now slow network API calls. Not necessarily. Caching and shared storage are real strategies. > Add to that container orchestration and all sorts of CNCF-approved things and the whole thing balloons. k8s is __not__ required for microservice architectures. > If you deploy this thing in a cloud, just networking costs alone will eat far more than your $20 Again, not necessarily. All major cloud providers have tools to mitigate this. To clarify: I'm not a microservice fanboy, but so many here like to throw around blanket statements with baked in assumptions that are simply not true. Sometimes monos are the right way to go. Sometimes micros are the right way to go. As always, the real answer is "it depends". |
Again, though: it does depend.