Book Image

Practical Microservices with Dapr and .NET - Second Edition

By : Davide Bedin
Book Image

Practical Microservices with Dapr and .NET - Second Edition

By: Davide Bedin

Overview of this book

This second edition will help you get to grips with microservice architectures and how to manage application complexities with Dapr in no time. You'll understand how Dapr simplifies development while allowing you to work with multiple languages and platforms. Following a C# sample, you'll understand how Dapr's runtime, building blocks, and software development kits (SDKs) help you to simplify the creation of resilient and portable microservices. Dapr provides an event-driven runtime that supports the essential features you need for building microservices, including service invocation, state management, and publish/subscribe messaging. You'll explore all of those in addition to various other advanced features with this practical guide to learning Dapr. With a focus on deploying the Dapr sample application to an Azure Kubernetes Service cluster and to the Azure Container Apps serverless platform, you’ll see how to expose the Dapr application with NGINX, YARP, and Azure API Management. By the end of this book, you'll be able to write microservices easily by implementing industry best practices to solve problems related to distributed systems.
Table of Contents (20 chapters)
1
Part 1: Introduction to Dapr
5
Part 2: Building Microservices with Dapr
11
Part 3: Deploying and Scaling Dapr Solutions

Building microservices with Dapr

How can Dapr help us build this e-commerce application by adopting a microservice architecture?

In this section, we will learn about the specific benefits Dapr brings to a microservice architecture. Let’s start by exploring them all and begin with loosely coupled microservices.

Loosely coupled microservices

With pub/sub in Dapr, we can achieve two objectives. Not only does Dapr make it transparent to use any of the supported messaging systems, such as Redis, RabbitMQ, Azure Service Bus, and Azure Event Hubs, but it also provides all the plumbing code that’s responsible for handling the message operations, ensuring at-least-once delivery.

Two microservices, signaling to one another an event via pub/sub, can coordinate via a loosely coupled connection. If the consumer is experiencing a temporary issue, the information that’s sent by the producer will stay safely in the messaging subsystem of choice, waiting for the consumer...