Tag
exactly-once
- Jun 3, 2026 Exactly-Once Delivery Across System Boundaries The dual-write problem, the outbox that removes it, and the narrow sense in which a message can be applied exactly once when the database and the broker are separate systems. backend systems
- Mar 13, 2026 Idempotency at the Effect Boundary, Not the Handler Entry Deduplicating a job at the point where it changes the world: unique constraints, request keys, delta-to-fact conversion, and the two-phase effect that survives a crash mid-call. backend systems
- Oct 22, 2025 Why Exactly-Once Delivery Stops at the Workflow Boundary How end-to-end exactly-once requires three coordinated commits, which participant in a scheduled workflow cannot supply one, and what the achievable guarantee actually is. data engineering
- Jan 13, 2025 Two-Phase Commit and Exactly-Once Sinks Why a stream job cannot deliver exactly once without the sink participating, and how a prepare-then-commit protocol ties checkpoint state to external writes. data engineering
- Jun 26, 2023 What Exactly-Once Delivery Requires at Each Hop The guarantee is a conjunction of idempotence keys, transactional positions, and source cooperation, and it terminates at the first hop that lacks any of them. data engineering
- Dec 5, 2022 Row Identity and Why Deduplication Needs a Key, Not a Comparison Deciding that two records describe the same entity requires a declared key; comparing whole rows fails on late-arriving corrections, and windowed dedup only moves the ambiguity. data engineering