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

Reviewing containerization fundamentals

While it is assumed that you have some experience with Docker already, it’s worth the time to quickly review some of the fundamentals of working with containers and some of the inherent benefits of using them. We will first cover the fundamentals of isolation, portability, reusability, layering, and abstraction.

Regarding isolation, Docker allows focusing on one process within the confines of a container. In the world of Docker, containers are immutable and are created from images that can be utilized directly from the Docker registry or can be used from a private registry for images that are custom built for specific needs. This notion of immutability allows for isolation to be confined to just the process that the container needs and not to any outside influences or mutations. That’s not to say that outside influences cannot modify things within a Docker container. The immutability comes in when a container is restarted, and...