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 1, The Sample Application

  1. Understanding the business perspective helps to tie real-world situations to conceptual designs as well as understand how behaviors of business objects can impact the need for resilient, scalable services to support them.
  2. It’s possible to theorize that there is a use case for a WorkOrders domain; however, the concept of WorkOrder may be better served as a supporting entity within the Maintenance domain.
  3. Every effort was taken to ensure no erroneous or excess information was included in the aggregates. Personal preference or strict adherence to prescriptive DDD patterns may cause that to shift.
  4. A traditional “relational” database tends to allow all forms of data manipulation, from inserts to updates to deletes while also structuring the data. NoSQL options allow for unstructured, heterogeneous data to be stored in the same logical data store. Using event sourcing strongly encourages the use of an append-only transaction...