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 3, Message Brokers

  1. Queue-based, cache-based, and stream-based.
  2. While AMQP is a popular messaging protocol, there are plenty of applications that use HTTP, TCP, MQTT, or other protocols to send and receive messages.
  3. Yes. Whether through a traditional request-response or more modern mechanisms such as WebSockets, HTTP is perfectly viable as a transport mechanism.
  4. This will depend on your overall application design choices and what works best for you and your team. Each approach has benefits and drawbacks.
  5. At-most-once is the most likely to be susceptible to data loss.
  6. Yes – so long as one functioning broker exists, a Kafka cluster can function.
  7. Zookeeper tends to the different brokers within the cluster by providing configuration data, determining the active broker through leader election, and more.
  8. No – topics can be created from the command line, using a GUI interface such as Kafdrop, or even programmatically via code when you...