Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Practical Microservices with Dapr and .NET

You're reading from   Practical Microservices with Dapr and .NET A developer's guide to building cloud-native applications using the Dapr event-driven runtime

Arrow left icon
Product type Paperback
Published in Dec 2020
Publisher Packt
ISBN-13 9781800568372
Length 280 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Davide Bedin Davide Bedin
Author Profile Icon Davide Bedin
Davide Bedin
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Section 1: Introduction to Dapr
2. Chapter 1: Introducing Dapr FREE CHAPTER 3. Chapter 2: Debugging Dapr Solutions 4. Section 2: Building Microservices with Dapr
5. Chapter 3: Service-to-Service Invocation 6. Chapter 4: Introducing State Management 7. Chapter 5: Publish and Subscribe 8. Chapter 6: Resource Bindings 9. Chapter 7: Using Actors 10. Section 3: Deploying and Scaling Dapr Solutions
11. Chapter 8: Deploying to Kubernetes 12. Chapter 9: Tracing Dapr Applications 13. Chapter 10: Load Testing and Scaling Dapr 14. Other Books You May Enjoy Appendix – Microservices Architecture with Dapr

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 for a microservice architecture. Let's start by exploring 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 Hub, 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 to come back and get it.

...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image