To me microservices should not be an architecture. You can have pieces of functionality in a monolith that make sense to scale independently, and those should

To me microservices should not be an architecture. You can have pieces of functionality in a monolith that make sense to scale independently, and those should not be micro, they should be meaningful pieces of functionality that justify the overhead of spinning them out. In a way your comment reflects this, a lot of the places that justified microservices were at a scale where their "microservice" was serving more requests than the average company's entire codebase. It's "big data" with 10 GBs of logs all over again.