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 8, CI/CD Pipelines and Integrated Testing

  1. Not necessarily. Depending on the needs of the component itself, you may only have to implement one or two of the CI/CD patterns discussed. It is good practice to at least ensure that you are separating environments and using an artifact repository.
  2. Normally, feature flags are seen as beneficial when working with an application that is driven by its user interface – that is, there is a primary user interface upon which the user experience is intended to be based. If your application is a set of microservices, for example, using feature flags may not be as relevant unless you have strict requirements to keep newer services relegated to only a specific subset of consumers.
  3. While approval gates are normally the first item to come to mind, another frequent gate is that of change management. As an example, organizations using ticketing systems such as ServiceNow to manage how they raise, approve, and execute change requests...