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

Enabling GitHub Actions for CI/CD implementation

In this section, we’ll be walking through how to set up the CI and CD pipelines for the Equipment domain. Once you’ve completed this example, you will be able to create the same pipelines for all other domain projects.

GitHub Actions for continuous integration

For the continuous integration setup, we will be starting with a basic template meant to build the source code, as well as run any applicable unit tests. Once complete, any required Docker images will be stored in GitHub Packages:

  1. Clicking on Configure will spin up a new CI pipeline template based on the output you selected. Figure 8.3 illustrates the pipeline template we will use in this example:
Figure 8.3 – GitHub Actions templates, as suggested based on the repository type

Figure 8.3 – GitHub Actions templates, as suggested based on the repository type

  1. Figure 8.4 shows the YAML pipeline created for you by GitHub when you click on the Configure button:
Figure 8.4 – Sample pipeline generated by GitHub when you click Configure
...