Eventlane makes consumer behavior explicit: idempotency prevents duplicate side effects, transient failures back off and retry, poison events move to a dead-letter queue, and repaired events can be replayed without pretending delivery is exactly once.
Model: at-least-once delivery + consumer-side idempotency + exponential retry + DLQ. It is intentionally deterministic and small; it does not claim broker transactions, exactly-once semantics, distributed ordering, or production Kafka/RabbitMQ behavior. Source and tests ↗