Why not exclusively employ sockets instead? While I refrain from passing judgment, I've encountered numerous WCF services that exchange XML documents. Can you fathom the latency involved in serializing and deserializing within such a system? Is there a significant drawback to utilizing C++ in the backend and handling binary files for enhanced efficiency?
Not sure what to intent of this video was, but from an introduction I would expect to get an overview, what problems does Dapr solve, why would I use it etc. For that this video is remarkably bad.
Dapr makes it incredibly simple to establish your microservices infrastructure, encompassing elements like tracing, logging, metrics, pub/sub brokers, state stores, integration with external resources, secret storage, and ensuring resilience, all while adhering to best practices.
Fantastic, looking forward to more videos on Dapr and radius from microsoft
Nice video!, I have a question, does DAPR support HTTP/2?
Why not exclusively employ sockets instead? While I refrain from passing judgment, I've encountered numerous WCF services that exchange XML documents. Can you fathom the latency involved in serializing and deserializing within such a system? Is there a significant drawback to utilizing C++ in the backend and handling binary files for enhanced efficiency?
Not sure what to intent of this video was, but from an introduction I would expect to get an overview, what problems does Dapr solve, why would I use it etc. For that this video is remarkably bad.
The problem domain was mentioned in the very beginning: microservices. You will need to be familiar with microservices to understand this video.
Dapr makes it incredibly simple to establish your microservices infrastructure, encompassing elements like tracing, logging, metrics, pub/sub brokers, state stores, integration with external resources, secret storage, and ensuring resilience, all while adhering to best practices.
thank you