* It's mostly technical concern that is blurring the business logic in the entity * Async interactions before stopping is often not needed * Implemented with an internal PoisonPill signal that is added by sharding, * Persistent actors handle PoisonPill and run side effects after persist and process stashed messages before stopping. * remove unecessary stop messages * reference docs |
||
|---|---|---|
| .. | ||
| main | ||
| test | ||