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

Implementing non-intrusive telemetry capture

The idea of implementing baseline telemetry without the incurred overhead of adding custom code was not something that many deemed possible years ago. With the advent of platforms such as New Relic, DynaTrace, DataDog, and Application Insights, simply adding a library reference to your project and configuring connection information can enable a good amount of service- and component-level telemetry without further configuration. Even with a small amount of configuration and coding, these platforms can capture and expose metrics, logs, and traces.

Options exist beyond those platforms to capture telemetry as well. A question that you may find yourself asking is, “why would we want to implement this instead of using Application Insights?” On the one hand, you may want to gather this information and feed it to a platform tool within your Kubernetes cluster. You may also want more detailed control over what exactly is captured...