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

Chaos testing

While chaos testing involves executing tests designed to break services your application depends on, the overall discipline of chaos engineering was first established in 2010 by engineers at Netflix. The primary purpose of this type of engineering was to test how their services and applications behaved under extreme circumstances. In 2012, Netflix open sourced Chaos Monkey, which was their internal chaos testing platform. This opened the doors for other companies and engineers to be able to leverage and modify that suite and adapt it to their applications.

The order of chaos engineering

Chaos engineering follows a simple set of principles, allowing there to be order within the chaos, so to speak. The three main principles of chaos engineering, according to Gremlin, are as follows:

  1. Plan an experiment: This step starts with a hypothesis you formulate based on how your application would respond to a problem or outage. This can depend heavily on your definition...