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

Containerization and Local Environment Setup

So far, we have seen that our modular solution design, with services implementing the Single Responsibility Principle (SRP), can quickly lead to a wealth of running components within our application. Working on these as a single contributor could be overwhelming, and working on isolated domain teams may lead to hiccups when performing integration testing. Establishing a pattern that will address the potential for issues during integration, along with a lower barrier to entry for developers, can pay huge dividends down the road. Throughout this chapter, we will be doing just that—setting up a pattern for usage and deployment that will carry on across developer environments and, ultimately, to production.

Throughout this chapter, we will be doing the following:

  • Reviewing containerization fundamentals
  • Setting up the local environment
  • Using Dockerfiles to build and run locally

By the end of this chapter, you...