These are chat archives for akkadotnet/akka.net
@aarondandy I see two main design patterns, depending on your use case:
1) Actors with identity (like users, games, devices, etc), when you need to evenly distribute actors across the nodes in a cluster. Also, see
passivation in cluster sharding for getting actor out of memory when they're idle.
2) Routers, for those cases in which you just need a bunch of actors to perform some work in a load-balancing fashion. If you need to route work with a certain key to the same routee, see the
Otherwise, I think you're pretty much on your own when it comes to managing an actor lifecycle.