Book Image

Practical Microservices with Dapr and .NET

By : Davide Bedin
Book Image

Practical Microservices with Dapr and .NET

By: Davide Bedin

Overview of this book

Over the last decade, there has been a huge shift from heavily coded monolithic applications to finer, self-contained microservices. Dapr is a new, open source project by Microsoft that provides proven techniques and best practices for developing modern applications. It offers platform-agnostic features for running your applications on public cloud, on-premises, and even on edge devices. This book 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 offers ease of implementation while allowing you to work with multiple languages and platforms. You'll also understand how Dapr's runtime, services, 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 to build 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. By the end of this book, you'll be able to write microservices easily using your choice of language or framework by implementing industry best practices to solve problems related to distributed systems.
Table of Contents (16 chapters)
1
Section 1: Introduction to Dapr
4
Section 2: Building Microservices with Dapr
10
Section 3: Deploying and Scaling Dapr Solutions

Discovering microservices

There is an endless collection of books, papers, and blog posts that excellently describe and analyze the microservice-style architecture. The objective of this chapter is to present you with the advantages and challenges of using a microservices architecture, to find out how Dapr can help us create new applications based on it.

The nemesis of a microservices architecture is the monolith: no one would ever admit they built or are still working on one. But most of us, in the development industry, spent many years working on monolith applications. In a monolith, as the name implies, all the business capabilities or features are condensed in a single application, probably layered between the UI, server, and database, but nevertheless not designed in a modular or distributed fashion.

In a microservice architecture, the services that are designed to support business capabilities are most likely to communicate with open protocols such as HTTP and gRPC, are...