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’ve explored the world of application resiliency, cloud-native design patterns, information redundancy to support business continuity, and the importance of clear and graceful communication. Using the Polly library, we have seen how different policies can be applied to method execution to promote resilience.

By using purpose-built services, we’ve seen how enabling event redundancy at each station can help protect information from becoming lost in the event of a communications failure. Also, we have seen how graceful service degradation can be augmented by graceful communication patterns, enabling user-centric feedback when things go amiss. As we look forward to Chapter 13, Telemetry Capture and Integration, we will take what we have learned with respect to resiliency and redundancy and augment it with telemetry capture to properly catalog information that can be used by operational teams later in the event of a platform issue.