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

Application- versus service- versus component-level telemetry

As covered in Chapter 7, Microservice Observability, we can collect simple telemetry by installing the Application Insights library as a dependency and configuring it to point to an existing Application Insights instance in Azure. This covers us at the code level for any immediate metrics, logging, or tracing that Application Insights can provide out of the box. While this is useful, we may need to break that down further and capture some specific baselines at various levels.

For our sample application, we would expect to capture telemetry at three different levels:

  1. Application – Telemetry at the application level would include the overall health of the application, as well as any critical failures and the ability to troubleshoot distributed services. This may also include infrastructure- or cloud-platform-related status indicators.
  2. Service – Telemetry at the service level would include measurements...