Book Image

Implementing Event-Driven Microservices Architecture in .NET 7

By : Joshua Garverick, Omar Dean McIver
4 (1)
Book Image

Implementing Event-Driven Microservices Architecture in .NET 7

4 (1)
By: Joshua Garverick, Omar Dean McIver

Overview of this book

This book will guide you through various hands-on practical examples for implementing event-driven microservices architecture using C# 11 and .NET 7. It has been divided into three distinct sections, each focusing on different aspects of this implementation. The first section will cover the new features of .NET 7 that will make developing applications using EDA patterns easier, the sample application that will be used throughout the book, and how the core tenets of domain-driven design (DDD) are implemented in .NET 7. The second section will review the various components of a local environment setup, the containerization of code, testing, deployment, and the observability of microservices using an EDA approach. The third section will guide you through the need for scalability and service resilience within the application, along with implementation details related to elastic and autoscale components. You’ll also cover how proper telemetry helps to automatically drive scaling events. In addition, the topic of observability is revisited using examples of service discovery and microservice inventories. By the end of this book, you’ll be able to identify and catalog domains, events, and bounded contexts to be used for the design and development of a resilient microservices architecture.
Table of Contents (21 chapters)
1
Part 1:Event-Driven Architecture and .NET 7
6
Part 2:Testing and Deploying Microservices
12
Part 3:Testing and Deploying Microservices

Debugging in containers

The container images can be started on demand to run the microservices. However, producing a new Docker image that internally builds and publishes release code will not offer the debugging of the code we are looking for!

To overcome this, we need to run the development code unpublished, using a Debug build, quickly and dynamically inside a container with a debugger attached. We must understand how Visual Studio modifies the container images to support debugging, and how this fits into the overall orchestration of all components, including the service component.

Debugging individual microservices

While Visual Studio did a fantastic job setting up the Dockerfile for release builds, it does not use this entire file definition when debugging code in a container.

The additional configurations added to the project enable exactly the kind of fast and dynamic environment we need. Under the project launch profiles, you should now see a new one added by Visual...