Adversarial / chaos testing for subscription guaranteed delivery #16

New issue

Closed

opened 2026-02-19 21:28:32 +00:00 by ash · 1 comment

ash commented

2026-02-19 21:28:32 +00:00

Owner

What

Prove the guaranteed delivery claim under adversarial conditions.

Scenarios

Kill consumer mid-batch → restart → no events lost
Kill store mid-write → consumer handles gracefully
Network partition between store and consumer
Clock skew
Extremely slow consumer (10x slower than write rate)
Random process crashes (chaos monkey style)
Sequence gaps from rolled-back transactions
Out-of-order commits (multi-writer)

Method

Inject failures via test doubles
Verify: every event written is eventually processed exactly as many times as expected
Count: total events written == total events processed (after recovery)

## What Prove the guaranteed delivery claim under adversarial conditions. ## Scenarios - Kill consumer mid-batch → restart → no events lost - Kill store mid-write → consumer handles gracefully - Network partition between store and consumer - Clock skew - Extremely slow consumer (10x slower than write rate) - Random process crashes (chaos monkey style) - Sequence gaps from rolled-back transactions - Out-of-order commits (multi-writer) ## Method - Inject failures via test doubles - Verify: every event written is eventually processed exactly as many times as expected - Count: total events written == total events processed (after recovery)