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

Adopting microservices patterns

What benefits does a microservice architecture bring to an application? Why should we move from monoliths to microservices?

Considering the concepts described so far, I think the following might be a good list of improvements you can achieve by adopting microservice architecture:

  • Evolution: It is common to have several smaller teams, each working with the tools, languages, and platforms that best match their objectives. By defining a simpler and smaller (bounded) context of the application, there are far better chances that its evolution and growth will be faster, more reliable, and have greater business impact.
  • Flexibility: By becoming as autonomous as possible, and by interacting with others in a loosely coupled manner, the microservice will gain many opportunities that would otherwise be impossible for a monolith architecture: changing the persistence layer, adopting a new library, or even switching to a different technology stack now...