In this article, we explore the various ways to structure your .NET solutions and applications, including microservices, monoliths, clean architecture, and shared databases. We analyze the trade-offs of each approach and provide examples of how to implement them. With so many choices, there is no one perfect decision, but rather a spectrum of architectural decisions that can be combined in different ways to optimize for development speed, explicit boundaries, and code conflicts. This article is part of 2022’s csadvent.
