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

Data consistency paradigms

The two primary consistency paradigms to be aware of are referred to as ACID and BASE. We will define these acronyms in the following sections and understand what they are and how they differ. To help remember these acronyms, we can use an analogy from chemistry, where a BASE is the opposite of an ACID.

ACID paradigm/immediate consistency

As previously noted, ACID stands for atomic, consistent, isolated, and durable.

With immediate consistency, we get a guarantee that each transaction will be completed as a single unit of operation. Therefore, it will either entirely succeed or entirely fail. Take a hypothetical scenario of a consumer ordering a product to a new delivery address. In an immediate consistency model, the typical process for this transaction would be to first issue the address change and wait for positive confirmation that it was validated and written to the customer’s profile. Next, the order would be created, at which point...