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

Configuring orchestration and containers

We are already orchestrating components of the application using container technology. The docker-compose.yml file that we have explored in previous chapters defines the supporting containers we need and their configuration. When we execute docker-compose with this file, we are orchestrating the dependency resources by spinning up a specific configuration of containers in Docker.

The next step is to add the MTAEDA microservices to this orchestration definition, so we can develop code efficiently and consistently.

Everything as Code (EaC)

For a moment, let us validate why we want to continue with an orchestration approach to support the EDA development. I am confident you know at least the basics of DevOps! (I am referring to the practice, not the Microsoft service). By now, you may have also heard of, or worked with, GitOps. If you have not – do not fear. At the heart of both practices, you will simply find code to describe every...