Gokul Chandra put together this tutorial on hot topic of microservices. Majority of the issues that developers often run into while developing microservices for edge or cloud, revolve around event-driven needs.
Dapr (Distributed Application Runtime) uses a side-car pattern which is similar to side-car implementation in service mesh architecture, where a local proxy is used to route requests. A key feature of Dapr is that it is completely platform and language agnostic, meaning that it can run on any platform, any Kubernetes deployment, in the cloud or on-premise, and even on any IoT device.
Dapr exposes its APIs as a sidecar architecture, either as a container or as a process, not requiring the application code to include any Dapr runtime code. This brings-in the advantage of having Dapr integrated with existing and legacy code operated through a standard HTTP/gRPC interface. This facilitates enterprise developers to experience the benefits of microservices development without having to rewrite their applications.
The article then explains:
- Dapr Kubernetes
- Dapr concepts
- Spec and service invocation
- Bindings
- Pub Sub and Broadcast
… and much more. Dapr today provides an extensive set of building blocks apart from service invocation and state management like: Publish and subscribe messaging between services, Event-driven resource bindings, virtual actors, Distributed tracing between services etc. Good read!
[Read More]