Don’t start with microservices. ❌ Even if you think your app will grow into it. Microservices come with a heavy premium: - More coordination - More failure modes - Eventual consistency - CI/CD complexity - Extra infrastructure - Multiple codebases to maintain None of that helps you deliver value faster — especially early on. If you can’t manage a well-structured monolith, microservices won’t save you. They’ll slow you down. A better approach: - Start with a modular monolith - Let clear boundaries emerge - Split only if needed Your architecture should evolve with the product — not the other way around. Here’s a deeper dive into building modular monoliths in .NET: https://lnkd.in/eBnhgRU2 Would you start a greenfield project with microservices? Why or why not?