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

Graceful communication between services

Everyone at some point has experienced an issue with a website or application where an error message will pop up that means absolutely nothing to the end user. Sometimes, it’s no error message at all. Other times, it can be a complete stack trace dump that appears in the error message. Either of these scenarios is far from optimal, as the impact on the user is detrimental and could potentially share information about the code base if messages aren’t adjusted.

The same can be true of messages tracked in logs. If no information is sent about a potential error or exception, finding out what happened – and how to fix it – becomes very challenging. It’s important not only to the usability of the system but the maintenance of it as well to have clear, meaningful messages meant for each type of audience.

A common way to manage exception messaging is through the development of exception types that derive from...