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 13, Telemetry Capture and Integration

  1. Sometimes, the platform used to capture telemetry is not at the developer’s discretion, and another means of capturing and analyzing the information will be used. Common examples include the ELK stack and Splunk. Teams may also want tooling that is independent of a particular cloud but common across a specific cloud service, such as Kubernetes.
  2. The Activity type is generally used during the course of method execution to capture information often found useful for tracing, while Meter objects are generally about capturing an occurrence or other frequencies over time related to actions within the code. How the information is measured is one of the primary drivers, along with the implementation model.
  3. Yes, each of those examples listed will factor into the overall design and usage of any telemetry capture platform. Depending on what is chosen, the cost can vary from data storage to transactions processed to individual licenses...