![]() Not overly helpful as far as day to day development goes, but after a dive into the samples I soon realized what a powerful tool it could be.ĭapr runs as a sidecar process to your main service process. So what is Dapr? To pluck a description straight from - Dapr is "An event-driven, portable runtime for building microservices on cloud and edge.". However, I soon realized this is a whole different ball game. On the mention of the word Dapr, my mind instantly jumps to ORM's and database-y things. I was recently listening to the Azure Dev Ops podcast and specifically the interview with Mark Fussell talking about Dapr. ![]() An entire app structured entirely on an event bus comes tumbling down when the event bus stops functioning. It's the most decoupled as far as knowledge is concerned, but also one of the more involved to set up compared to gRPC and REST ('dotnet new webapi' anyone).Įvent-based communication gives a single point of failure though. It's for this reason, I've always tended to gravitate towards event-based communication. For the order-service to make a GET request to the product-service it must have some knowledge about where to send that request. One of my biggest gripes when building microservices is the knowledge each service must-have of any other service it needs data from (event bus-based communication aside). Last week I wrote an article discussing the different faces of microservice communication.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |