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

Data loss implications

There are many scenarios we could evaluate to find the optimal delivery guarantee for a given process. As an example, each time a mechanical barrier counter increments, this is sent via an event to the maintenance tracking service. If each event simply contains a barrier ID, then we have the decision to make in the accuracy of the counter driving the maintenance schedule.

At-most-once delivery will ensure we do not overcount the use of each barrier due to system failures that would otherwise result in duplicate events. However, it also means we might undercount for the same reasons. This could result in late maintenance, meaning a higher probability of barrier failure.

At-least-once delivery will ensure we do not miss any counts in the use of a barrier. However, it also means we might overcount through duplicate (retry) events. This could result in early maintenance, meaning a higher cost to operate. It will also impact system scalability and throughput...