Message Passing and the Actor Model
I haven&#x27;t given myself the opportunity to sit down and play with an actor model. But in the meantime, despite reading literature such as this, I have trouble envisioning what it actually entails day-to-day.<p>I think of my experience with channel-based communication in Clojure, Go, and even Rust&#x27;s mpsc. And every time I feel an instant feeling of debt because I know I&#x27;m just one or two more channels away from misunderstanding the execution of my own application. Having to take out pencil and paper to reason about why messages are bottlenecking in this component or why I was wrong when I thought I knew how my application worked.<p>For example, we ripped out all of our channels in our Go application and replaced them with a couple mutexes.<p>When I read about actors, I get flashbacks to some of my worst struggles with channels. Where our application is split into disparate agents that everyone has to eventually map out on a whiteboard to understand even basic runtime behavior.<p>I owe it to myself to try it out, but I can&#x27;t help but be discouraged by what I think they are. Can someone clarify? What does the actor model actually mean for your day-to-day code compared to futures, for example?