Adding a Little DAPR to Your .NET Microservices

Показать описание

DAPR makes building distributed applications much easier by providing a collection of language agnostic building blocks that can be used in any cloud or on-prem environment. In this session, we'll dive into DAPR, discuss the various build blocks it supports, and see some demos of how you can make use of it in your .NET applications.

dotnet
.NET

Рекомендации по теме

Комментарии

That was a very nice and clear explanation. Thank you very much!

DuncanRoosma

Very nice project, very clear presentation. Thanks a lot

PaulVanBladel

I'm still not sold on dapr. When you have a generic interface for every type of service (pubsub, store, etc) you have to use a common denominator that each underlying service can support. Which means it supports the bare minimum of each service. I would also like to see some performance reviews of overhead using dapr vs not using it (or microservices in general)

Edit: I watched the questions at the end and @rerun_adam hit my exact question. Dapr is a highly opinionated framework, so if you want to use a custom feature of the underlying tech you are out of luck. I'll be looking elsewhere for needs in the future. Side note, it's crazy how many times Microsoft has reinvented the actor framework. Orleans, Service Fabric, Dapr. Even when there are well established players in the market like akka.net.

Gonkers

Thanks. Great presentation... only worry is we are leaving everything to the runtime to decide. In your example how do I annotate dapr to use Redis instead to rabbitmq for your scenario?

chandrag