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?
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.
I started out using Akka.Net and then tried Orleans, and IMO, Orleans is a lot better for what I need(virtual actors), but Akka is still good. MS also has Coyote which has the Actors from MS Research, which I'm looking at to use in systems not completely Actor based. So yes, they have a lot of actor systems. DAPR isn't clear to me yet.
That was a very nice and clear explanation. Thank you very much!
Very nice project, very clear presentation. Thanks a lot
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?
Absolutely fantastic! Thank you!
Very well explained, Cecil. Can you share the source for learning? Thanks.
github.com/dapr/docs
Nice presentation ✌
Hi Cecil.. nice video. Does Dapr integrate with RedHat OpenShift ?
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.
I started out using Akka.Net and then tried Orleans, and IMO, Orleans is a lot better for what I need(virtual actors), but Akka is still good.
MS also has Coyote which has the Actors from MS Research, which I'm looking at to use in systems not completely Actor based.
So yes, they have a lot of actor systems. DAPR isn't clear to me yet.
Is there a source code available for this? (Github)
github.com/dapr/dapr
github.com/cecilphillip/ContosoCrafts/tree/dapr
Why would I ever want service invocation feature of Dapr?
Love Dapr. But it cannot a little. It requires you must have Kubernetes to deploy.
Can someone please provide a step by step implementation documentation for this?
github.com/dapr/dapr