One of the things this article alluded to (but I didn't see it explicitly stated) as to why microservices is a default go-to architectural choice: Because then

One of the things this article alluded to (but I didn't see it explicitly stated) as to why microservices is a default go-to architectural choice: Because then a bunch of engineers can stick it on their résumé and try to get a job at a big company I worked in a funded startup where we built a service-oriented architecture out of a few key Laravel monoliths. This was entirely manageable for a team of less than 10 engineers and scalable for the context. Because we built it as a distributed system, each of those core services was ready to handle outages. So it was extremely easy to deploy What's more, it barely cost us $20k PER YEAR to run it all But now I can't say I've worked with microservices so I'll likely not stand a chance at any of those interviews