.NET Aspire is sometimes referred to as being for microservices architectures. It certainly does support systems of that type of architecture pattern, but it is not only for it. The primary consideration for the appropriateness of Aspire is not the type of architecture, but the presence or absence of multiple resources that need to run in different processes and with different storage requirements. In designing your systems, there are several factors that go into making good choices on the types of resources to include, including the structure of your teams and organizations. .NET Aspire does not dictate architecture choices, but it’s worth thinking about what your system needs to support and using .NET Aspire to articulate a model for your system design to optimize the developer experience and to guide thinking about deployment.