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

Configuring Dapr policies with API management

To reach our goal, we have to create an API first and then a set of operations, not forgetting to deploy the API to our self-hosted gateway.

To have a good understanding of the terminology of APIM, I suggest reading the documentation at https://docs.microsoft.com/en-us/azure/api-management/api-management-terminology.

Let’s create an API first, as shown in the following screenshot:

Figure 10.5 – Creating an API

As depicted in Figure 10.5, I chose to configure the API; the API named BBmB API has a /api URL suffix. It is present in all the default products (this is just to simplify the scenario), and I would like to deploy it only to the self-hosted gateway named daprgateway we created in the previous section.

With an API defined, we are now ready to create our first operation to check whether everything works as expected. The following screenshot highlights how to do this:

...