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 7, Microservice Observability

  1. Kubernetes will continue to check the liveness endpoint. If it fails for longer than the configured tolerance, the Pod will be terminated. If the Pod is part of a deployment, it will attempt to create a new instance of the Pod.
  2. Kubernetes will continue to check the readiness endpoint. If it fails for longer than the configured tolerance, Kubernetes will stop sending any requests to the Pod until the readiness endpoint succeeds again. In a deployment with multiple replicas, other Pods will share the incoming requests so long as their readiness endpoints succeed.
  3. A correlation identifier will be consistently reported across the event logs related to a specific triggering action.
  4. A causation identifier will be reported for each event, indicating the prior event that triggered the current event. This is a tree-like hierarchy, as one event could trigger multiple next events – especially using the publisher-subscriber pattern...