The actor model is a popular approach to building scalable software systems. And isn't hard to understand when you're just reading about the beginner's examples. But how do you architect a complex design using the actor model? Which patterns work well? How do you think through it? Joining me to take us through it is Hugh McKee. Hugh's a total actor-model fan, and a Developer Advocate for Lightbend (the company that created the popular actor framework Akka). He takes us from his definition of actors to the designs he's worked on, the patterns he's found most useful, and the interesting meeting-point between actor-based designs and event-based ones. — Wikipedia - Actor Model: https://en.wikipedia.org/wiki/Actor_model Hugh's book, Designing Reactive Systems: https://go.lightbend.com/designing-reactive-systems-role-of-actor-model Hugh on Twitter: https://twitter.com/mckeeh3 Hugh on LinkedIn: https://www.linkedin.com/in/mckeehugh Kris on Mastodon: http://mastodon.social/@krisajenkins Kris on LinkedIn: https://www.linkedin.com/in/krisjenkins/ Kris on Twitter: https://twitter.com/krisajenkins