Your MVP Doesn't Need Microservices. It Needs Customers.
Somewhere between installing Docker and configuring Kubernetes, we forgot to build the actual product. Let's imagine you've got a startup idea. You've identified a problem. You've spoken to a few potential customers. You're excited. You open your laptop, create a new repository, and start building. So far, so good. Then comes the architecture discussion. "Should we use microservices?" "Maybe Redis for caching?" "We'll need a message queue." "What about Kubernetes?" "Should we separate authentication into its own service?" Three hours later, you've got a beautiful architecture diagram, 14 boxes, six arrows pointing in different directions, and absolutely nothing a customer can use. But hey, it's scalable. Scalable for what, exactly? Your two test accounts? Welcome to one of the most entertaining traps in software development: building infrastructure for a product that hasn't proved it needs infrastruct...
