Learning how to use Dapr bindings

In previous chapters, we devoted most of our attention to the Dapr architecture, and how to use its building blocks to facilitate communication between microservices in the context of the Dapr environment.

With Dapr’s service-to-service building blocks, we can directly invoke another microservice as the Dapr runtime takes care of routing requests to their destination and handling retries, among other benefits.

By managing the state, Dapr lifts from our microservice the responsibility of maintaining the plumbing code and the libraries necessary to interact with a persistence layer.

By supporting the pub/sub pattern, Dapr enables microservices to communicate in a loosely coupled fashion and allows our overall architecture to grow in complexity, minimizing the impact on existing portions of code.

All these building blocks focus inward on our microservices, although often, the architecture is not completely isolated as there is a need...