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

Chapter 9, Fault Injection and Chaos Testing

  1. A fault is something that occurs within a circuit, computer hardware, operating system, or other hosting mechanisms that cause a failure that cannot be recovered from easily. An exception is generally seen as a construct within software development where an error occurs during execution, which may or may not be expected.
  2. A common fault that can be anticipated and handled is that of a regional service outage for a cloud-native service. For example, if there is an outage affecting App Services in the US East region of Azure, this could be handled by keeping a secondary copy of those App Services in another region and configuring them to be available in the event of such an outage.
  3. Fault injection can be seen as an isolated discipline. However, in the software world, it doesn’t have to be. Using fault injection as a method to carry out chaos experiments is one that is commonly used to illustrate the interconnected role that...