Reg. the architecture question: People generally start carving out microservices once they hit some scale. What about starting off with microservices (because

Reg. the architecture question: People generally start carving out microservices once they hit some scale. What about starting off with microservices (because tools like k8s make the otherwise insane management overhead more tractable)? Could that be a possible solution? The problem of scaling state, databases need to handle anyway. Ideally the same database just keeps on working as you go up. Or atleast the protocol is the same, and you switch out the implementation from a single instance to a clustered version.