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

Service publishing

Now that we have an API, an easy-to-navigate specification for it, and a service discovery layer that manages the distribution of requests to healthy service instances, developers just need to know where to look for our service. This is where Service Publishing comes into play.

You can think of service publishing as a directory to search for, or simply browse, services that want to be discovered for use. If you are old enough to know what the white pages are, that is a close analogy. Only, imagine that this directory not only helps you look up services, but manages security, offers advanced monitoring, and can even add a façade that allows API requests and responses to be translated on the fly. A façade could even call multiple APIs on the backend with a single composite API endpoint on the frontend. Many even support the mocking of APIs, so you can take your design-first approach, build an OpenAPI specification, then have one team implement a simple...