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

Setting up API management on Kubernetes

First of all, why would you consider adding an API management service to your architecture?

In Chapter 3, Microservices Architecture with Dapr, we explored many concepts, including the relevance of the contracts we, architects of our solution and therefore of its external API, implicitly sign with our consumers.

To simplify a complex topic, great care should be taken in evolving an API on which other applications and systems depend; the way our overall solution changes over time, in terms of architecture, language, or frameworks, should never impact any external consumer in an unplanned or—even worse—an unexpected way.

As architects and developers, how can we manage the external API so that it does evolve to match objectives and at a different pace than our internal microservices? A great tool at our disposal is an API manager: a powerful way to manage the life cycle of an API, starting from its creation, documenting how...