A grants team asks for exactly-once end-to-end processing of every subsidy event across producers, Kafka, and multiple sinks. What tradeoff should architects communicate?
Select an answer to reveal the explanation.
Short Explanation
Wanting every subsidy event once sounds tidy, but end-to-end exactly-once is the fancy clockwork—pricey and intricate. At-least-once plus careful sinks is often the practical civic path. Know the tradeoff exists.
Full Explanation
Exactly-once semantics across an entire producer–broker–multi-sink path demand stronger protocols, idempotent sinks, and operational complexity than common at-least-once designs. Disk capacity alone does not buy end-to-end exactly-once, and at-least-once can still produce duplicates that consumers must handle. BDPC-level awareness is recognizing the ambition-versus-complexity tradeoff, not implementing a vendor deep-dive certification lab.