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

Choosing an Integration Test Suite Methodology

Just as there are preferred methods for identifying and writing unit tests for your code, there are similar methods for identifying and writing integration tests. As a general rule, integration tests are tests involving real instances of services, components, or other dependencies as opposed to mocks or stubs, which are often found in unit testing.

Several methodologies are considered standard when it comes to integration testing (source: https://softwaretestingfundamentals.com/integration-testing/). These include the following:

  • Big-bang: All components are combined together and tested at the same time
  • Top-down: Top-level units are tested first, then lower-level units are tested (that is, testing an API route and then testing the components that the route relies on)
  • Bottom-up: Lower-level units are tested first, then top-level units are tested (that is, testing component interaction before testing an API route that relies...