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

Summary

In this chapter, we covered a great deal of ground discussing the producer-consumer pattern. Not only did we define what a consumer is and what a producer is, but we also looked at how to implement messaging functionality in .NET 7, allowing both of them to interact with Kafka. We explored some features of the messaging platform infrastructure along with Kafka-specific features that allow for storing, transforming, and forwarding records.

With the knowledge of the producer-consumer pattern, as well as working on the code and infrastructure to support that pattern, you have established a good base understanding of how this messaging pattern can be implemented. Our next chapter centers on a specific construct within event-based messaging platforms—the message broker. The knowledge you've gained in this chapter will enable you to dive deeper into brokers and gain an understanding of how they are used in the larger scheme of event-driven systems.   ...