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

Chapter 4, Domain Model and Asynchronous Events

  1. The maintenance domain.
  2. The primary reason for using the mediator pattern is to decouple the producing and consuming code, allowing for a specific object to manage communications and reducing dependencies that could couple those consumers and producers together. The sample application uses the INotification and INotificationHandler<T> interfaces to differentiate event handlers within the domains and allow for known actions to be taken when an event handler is invoked.
  3. No – asynchronous programming, as seen with the async/await pattern in C#, does not automatically create new threads when an async method is called. New background threads can be spun up as a result of an async method when using Task.Run() or Task.Factory.StartNew() to create a new task.