Make compensation idempotent when its success response disappears and the triggering message returns.
A saga test that stops after “payment succeeded, inventory failed, refund called” assumes compensation is reliable. It is another distributed operation, so test it under the same faults.
Use this sequence:
1. payment capture succeeds
2. inventory reservation times out
3. refund succeeds at provider
Use a deterministic simulator to find duplicate refunds, late successes, and compensation failures.
Tune saga step timeouts, retry budgets, and compensation triggers across Java services without redeploy. Shared Kiponos tree with…
One-liner: In microservices, you can't use a single database transaction across services — the Saga...
Covers: Two-Phase Commit, Saga Pattern, Choreography vs Orchestration Sagas, Compensating...
There's a version of this story that plays out at almost every fintech startup I've worked with: the...
We had a checkout test at my last job that everyone called "the coin flip." Green for a week, red...
