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 2, The Producer-Consumer Pattern

  1. Yes; if producers were the only piece in existence, events could be written but never used. If consumers were the only piece in existence, no events would be produced for the consumers to consume.
  2. There can be several obstacles around the adoption of the producer-consumer pattern and event-driven architecture. Moving from traditional client-server applications to decoupled event-driven components can take time, especially for those who have coded in a particular methodology for years. Existing application code can also hinder adoption as it might seem overwhelming to think of how much would have to change to embrace this new architecture. Not everyone learns at the same pace, so having realistic expectations about adoption can only help drive its success.
  3. Minimal APIs are useful because they allow you to define routes and other functionality directly in the Program.cs file, which can help reduce the need to comb through source files...