The need to simplify the architecture of our monolithic solutions has led to modularization and the separation of logic into multiple smaller units, to the point of microservices and serverless implementations. While the benefits are many, there are also drawbacks (as always). The communication between the modules is harder to implement, as is the deployment. To tackle it, a new class of tools has emerged in the form of containers, Docker, Kubernetes, and serverless cloud platforms. This was great for production environments, but a lot broader knowledge is required from the developers nowadays – familiarity with DevOps and cloud platforms. Built on the foundation of Project Tye experiment, Microsoft has introduced .NET Aspire. .NET Aspire is first and foremost a set of tools to help with the development flow. It lifts the burden of complex local setup and configuration, just for the sake of being productive. With Aspire integrations, developers can just pull the latest source and run the solution with all the dependencies. Not just that, but it also provides production-ready configurations for dependencies and your own code, includes service discovery, and provides a dashboard with OpenTelemetry baked in. Oh, and it also helps with the deployment. This talk is an introduction to .NET Aspire and provides use cases and lessons learned while implementing it in client projects.

In this talk, you will learn all there is to know about various types of software architectures that are used in .NET ecosystem today and be ready to select a proper one when starting a new project. Of course not! Are you kidding?!? Nobody can teach you architecture in 45 minutes. This is not Matrix! We are in a blue pill world. Software Architecture is an elusive topic. When you read or listen about it, it makes sense, and you see how it can apply to your projects. However, the real learning starts when you start following it and implementing it. You need to go through the trenches of the actual usage and implementation to see the good, the bad and the ugly. Some even wander into an enemy territory of accumulated bad decisions and get shred into pieces with unexpected technical debt. And guess what? Even if you find a perfect match for your current project, it might not work at all for the next one. We will go through some of the most popular architecture concepts that .NET ecosystem lately nurtures (Clean Architecture, Hexagonal Architecture, Vertical Slice Architecture, Monoliths, Modular Monoliths...), and talk about pros, cons, and lessons learned on real projects.