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

Fault tolerance and fault injection

The concept of fault tolerance – that is, the ability of an application, platform, or runtime to tolerate a systemic fault – by itself seems a simple enough concept to grasp. After all, you would expect an application to be able to gracefully recover if certain services were not available. In many cases, though, applications have been written with an understanding that the underlying infrastructure that hosts it is always available unless a catastrophic event occurs. While this reliability may be built into on-premises data centers and rarely challenged, the same assumption does not hold for cloud platforms, services, and components.

Though cloud platforms will offer certain Service-Level Agreements (SLAs) for uptime on some cloud services, there is always the possibility of a service-level or region-level outage that can come with no warning and vary widely in impact. Therefore, it is important to keep these types of outages in...