I actually wanted to post the same thing. Alan Kay's view of OOP is mostly just the actor model. But the actor model, like OOP, does not tell us how to actuall

I actually wanted to post the same thing. Alan Kay's view of OOP is mostly just the actor model. But the actor model, like OOP, does not tell us how to actually build programs. "When do I use an object?" is a question OOP does not answer, "When do I use an actor?" is similarly not answered by the actor model. Service Oriented Architecture is also effectively the actor model, but with a focus on the persistent process abstraction. What Microservices does is take the actor model and say: * Here's how you figure out where the actor abstractions should go, how large they should be, and patterns for interaction Where microservices soooort of diverges is in its lack of discouragement of synchronous communication. But if you build your microservices using queues, I think you get the right sized actors with all of those benefits, without going down a rabbit hole of trying to structure every single bit of logic as an actor. AWS's "Cell Based Architecture" is also just actors, but with its own set of patterns for how large to build them.