I think that the actor model and micro-services solve entirely different issues. The problem that micro-services solve is not parallelization of computations, but organizational scaling.
In a tech organization with 80 developers working on the same product, it's easier to split the services into mostly independent and self-contained smaller services than can be developed and maintained by a small team.
While it is technically possible to have everything in the same application and have every team commit to the same repository and deploy everything together, splitting it into smaller chunks gives each team more autonomy and the possibility to adapt and set up different processes for different services.
I think that the actor model and micro-services solve entirely different issues. The problem that micro-services solve is not parallelization of computations, but organizational scaling.
In a tech organization with 80 developers working on the same product, it's easier to split the services into mostly independent and self-contained smaller services than can be developed and maintained by a small team.
While it is technically possible to have everything in the same application and have every team commit to the same repository and deploy everything together, splitting it into smaller chunks gives each team more autonomy and the possibility to adapt and set up different processes for different services.
Actually, localised autonomy is also very important in the Actor model as well: youtu.be/e5kek8vx2ws?t=1593
So I think the overlap could be quite good.