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

Localized Testing and Debugging of Microservices

From the previous chapters, we understand that the MTAEDA application sample code currently contains a mix of runtime components: two self-coded microservices (Producer and Consumer), and three supporting services (Zookeeper, Kafka, and Kafkadrop). We saw that the Kafka service is configured with a level of redundancy. However, to leverage the full performance potential of EDA, we must be able to scale all the services by adding more instances in an orchestrated pattern.

This provides us with a configuration management challenge that is common across all modern application development practices today – not just for EDA:

  • How do we develop and test efficiently with so many components to manage?
  • Can we provide multiple developers and teams with a consistent environment?
  • Will higher environments be reliably consistent with the development environment?

This chapter intends to walk through adding the configurations...