Arsene

That will be very useful.

@qazwsxedckll. Thank you so much for this issue. There is already an issue I created some time back to tackle that. You can find it [here](https://github.com/Tochemey/goakt/issues/192). At the moment, I...

@qazwsxedckll one can spawn an actor remotely with some caveats. :) kindly check the release note https://github.com/Tochemey/goakt/releases/tag/v1.6.0

> First of all, I am so impressed by your hard work, the documentation is very clear and the code is very clean. To my understanding, the problem now is...

@qazwsxedckll the challenge Go-Akt is having is to be able to serialize the `Actor` implementation so that we can pass it over the wire. There are various approaches to that...

@qazwsxedckll I will take a deep look into this use case. However a PR will also be welcomed in case you think of something that you would like to share....

@qazwsxedckll This was what I meant: - A node dies. In the redeployment case all the actors on that nodes will be moved to another node and started. When it...

@qazwsxedckll I will start some draft work on the redeployment feature. However I cannot promise when it should be ready because I need to dig a bit in [Olric](https://github.com/buraksezer/olric) capacity...

> I saw the RemoteSpawn method, all it need is the actor type and the actor name. I do saw that the Register method is not automatically called when starting...

# Design consideration - start the actor system with all the types of actor the system will be handling - each node to have the list of its peers -...