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

Microservice Observability

In the last chapter, we were able to orchestrate the MTAEDA application so that it is easy to launch and debug all the components of the system. Every individual service is available for interrogation at runtime, so it is easy to identify issues and gain the necessary insight to resolve them.

Eventually, the MTAEDA application will reside in several other environments outside of active development. When the application doesn’t work as expected, it is vital to be able to observe what is going on internally. Classically, monolithic applications produce cohesive serial logs that can be observed as needed.

Observability is critical to the speed of the overall development life cycle in quality assurance and user acceptance testing environments. When more effort is required to find out what is happening during an application failure, this ultimately prolongs the development of a fix and the subsequent testing to verify that fix. DevOps cycles are ground...