These are chat archives for akkadotnet/akka.net
Hey everyone, I'm a total n00b question here (but I've tried to do some research first, the bootcamp was awesome).
I've got a etag system backed by redis at the moment which needs refactoring. It seems like a nice and simple system to try out as an akka.net microservice.
Is a recieve timeout the right way to implement an actor which deletes itself? Kind of like a cache timeout?
Also, does akka ever cleanup actors which are completely idle or is this completely left to the developer? (I'm still wrapping my head around the lifecycle, as much as I'm told to ignore the idea of actors being active I want make sure I'm not doing something wrong).
Thanks for your help!
/user, it's a system actor, so it's messages won't affect your business logic consistency
Askthe actorref directly
a user can still add non breaking change, by adding a property and not changing the constructor