After talking to a colleague who has a lot of experience with Akka clustering, it seems this feature would be well-received by those looking for Akka clustering alternatives. In Akka, passivation works with persistent entities: if an entity is not being used, it can be stopped to reduce memory consumption. Looking through the documentation, it could be done by:
Setting a timeout on receiving messages (context.setReceiveTimeout in Akka)
Automatically through a config by providing passivation strategy options (e.g. idle entity passivation, limits on the active number of entities, etc)
I don't know if there's an implementation in the works for this, but in case there isn't but there is some interest for it, I'd be happy to take a crack at it.
After talking to a colleague who has a lot of experience with Akka clustering, it seems this feature would be well-received by those looking for Akka clustering alternatives. In Akka, passivation works with persistent entities: if an entity is not being used, it can be stopped to reduce memory consumption. Looking through the documentation, it could be done by:
context.setReceiveTimeout
in Akka)I don't know if there's an implementation in the works for this, but in case there isn't but there is some interest for it, I'd be happy to take a crack at it.