Summary
In this chapter, we explored the I/O binding building blocks of Dapr, and we learned how, with Twilio output binding, we can notify customers via text message without having to deal with libraries, SDKs, and the plumbing code, as it all boils down to a simple call to the Dapr runtime.
We then established a communication channel between a microservice of our sample e-commerce architecture with an external subsystem; both are unaware of each other’s implementation details, and our microservice is unaware of how to interact with Azure Event Hubs as the messaging bus.
The reservation-service application is placed at the center of our sample architecture, unlike the other microservices.
As a point of attention, the sample code doesn’t deal with application-level retries, which could be relevant if the strong consistency of state management and an elevated request rate prevent a reservation from always completing nicely. While this condition should be addressed...