Akka ReliableDelivery retries: where should deduplication state live to keep writes unique?
We are designing a typed Akka service where a producer actor sends commands to a consumer that performs a database write. Since Akka messaging is at-most-once by default, any retry mechanism (supervision restart, explicit resend, or ReliableDelivery redelivery) can deliver the same logical command more than once, so the write must not be duplicated. The plan
akka