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

Delivery guarantees

Event brokers typically provide several methods of delivery guarantees. Through the interfaces used to both produce and consume an event (API or SDK), the event broker can ensure how messages are delivered:

  • At-most-once delivery
  • At-least-once delivery
  • Effectively once delivery

The delivery method we choose for any given event depends on which benefit we want to achieve. As we explore each delivery method, we will explore examples that highlight the benefits and trade-offs of each.

At-most-once delivery

At-most-once delivery means that the broker will ensure that a produced event is only delivered at most once (obvious, right?). What this means is as soon as the first consumer processes the event, the broker will not deliver the event to any other consumer. It is at-most-once delivery, so there is a possibility that an event will never be delivered:

  • First, the producer does not wait for acknowledgment from the broker that an event...