Dapr.pdf
- 1. By : Vishwas Narayan @vishwasnarayan5 Vishwas N https://hacksterdude.web.app
- 4. The Complexity is coming up with these factors ● Geography ● Availability ● Connectivity ● Accessibility with the Engineers ● Telemetry ● Logs actually “Behavior of Logs”
- 5. Challenges ● How do Services Communicate and Discover Synchronously? ● How do they communicate Asynchronously communicate with respect to the Services? ● How can they maintain the contextual Information across transactions? ● How do they become resilient to the failure? ● How to Stress test and not break? ● How not to break in the Highest Traffic Scenario?
- 7. Take some Reference here (3) "dapr vishwas narayan" | Search | LinkedIn dapr.io Some blogs from Medium
- 8. So basically every body architects based on
- 9. So what is “Dapr” A portal Event driven runtime for building distributed applications across cloud and edge.
- 11. The magic of the best language
- 16. dapr/components-contrib: Community driven, reusable components for distributed apps (github.com)
- 17. Microservices in Service Invocation In many microservice-based applications multiple services need the ability to communicate with one another. This inter-service communication requires that application developers handle problems like: ● Service discovery. How do I discover my different services? ● Standardizing API calls between services. How do I invoke methods between services? ● Secure inter-service communication. How do I call other services securely with encryption and apply access control on the methods? ● Mitigating request timeouts or failures. How do I handle retries and transient errors? ● Implementing observability and tracing. How do I use tracing to see a call graph with metrics to diagnose issues in production?
- 29. So now lets See a “DEMO”