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

Using asynchronous actions

There are plenty of use cases for implementing synchronous actions within an application. At some point, those synchronous actions will not be able to scale out should the load on the application increase. This is where asynchronous actions come in. These actions allow many executions to be made using different contexts, whereas synchronous actions will block other actions from executing until the invoked action is complete. This ability to execute without the need to wait for a response allows large-scale message sending without any concern of thread-blocking, which can lead to longer wait times and less than desirable performance.

The notion of asynchronous actions has been a paradigm in programming for many years. Using callback functions, which are meant to be executed when one method has completed and returned a value, has been a construct in JavaScript, as well as other languages. Specific patterns such as asynchronous JavaScript and XML (AJAX) were...