Summary

In this chapter, we learned that the actor model that's supported by Dapr is a very powerful tool in our toolbox.

We understood the scenarios that benefit the most from applying actors, and how to avoid the most common implementation pitfalls.

By configuring Dapr Actors, from the state store to the ASP.NET perspective, we appreciated how the simplicity of Dapr extends to this building block too.

Next, we introduced an actor type to our existing architecture. By doing so, we learned how to separate the contract (interface) from the implementation and invoke it from other Dapr services.

Note that this is another example of how Dapr facilitates the development of microservice architectures by addressing the communication and discovery of services (how easy is it for a client to interact with an actor?). It also unleashes the independent evolution of our architecture's components; introducing actors in our example has been seamless for the rest of the services...