Separate transport, domain logic and storage so each is testable. Put slow or failure-prone work behind a queue with at-least-once delivery, and design consumers to be idempotent. Persist checkpoints so a restart resumes rather than reprocessing everything.
← Go theorytheory 0/50 · 0%
Design · hard
49. Architecture for Chain Services
Layering, queues and idempotency.
Check your understanding
1. At-least-once delivery requires consumers to be…
2. Checkpoints exist to…