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 12, Service and Application Resiliency

  1. Resiliency refers to an application or platform’s ability to handle faults, exceptions, or other problems that may arise. Redundancy refers to the duplication of data or services (or both) to help protect against data loss due to network issues or in the event of a disaster. Reliability is a measure of confidence in a platform or application’s ability to operate consistently.
  2. Both fallback and circuit breaker patterns allow you to stop execution and return a value that can be used in lieu of the expected operation. Fallback patterns will not perform any additional logic to allow further operations to continue on the same target, whereas circuit breakers will pause execution for a set amount of time and reset once the threshold is met.
  3. It allows you to retry operations that may fall victim to timeouts or other connectivity issues, either through graduated wait times or by coupling with other patterns to manage...