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 some fundamental lessons around the CI and CD of our domain services. We examined some common patterns, such as environment-based deployments, using artifact repositories to store build artifacts for later use, and more advanced concepts such as triggers, gating, and feature flags. We explored how to set up initial CI and CD pipelines using GitHub Actions, including the use of GitHub Packages for storing our artifacts once the builds are complete. We rounded out our pipeline discussion by reviewing some common types of integration testing, and how those tests could be added to our pipelines to further automate our testing and ensure quality is baked into our pipelines.

In the next chapter, we will be taking our testing game even further by incorporating fault injection and chaos testing into our pipelines. This is just one aspect that can help us identify issues with application resiliency and reliability, which is critical when dealing with an...