Actor Model - Senior¶
Actors move concurrency risk into mailboxes, supervision, ordering, and distributed placement.
flowchart TD
Child[Worker fails] --> Policy{Failure policy}
Policy -->|transient| Restart[Restart with bounded backoff]
Policy -->|bad input| Stop[Stop and quarantine]
Policy -->|systemic| Escalate[Escalate and shed load]
Use bounded mailboxes, dead-letter monitoring, explicit restart limits, and idempotent message handlers. Remember that messages from different senders may interleave. During cluster sharding, entity movement can overlap retries; use stable identities and deduplicate effects.
Test poison messages, slow actors, node loss, split brain, passivation, and restart with a full mailbox. Monitor mailbox age rather than only count.
Continue to professional.md.
Test yourself¶
- When should supervision restart versus stop an actor?
- Why is sender-local order insufficient for global order?
- Which metric exposes a slow actor earliest?