Multiple ChoiceIntermediate 45s
Exactly-once reality
What does 'exactly-once' typically mean in a streaming system like Kafka with transactions?
Options
- 1Effectively-once processing within the system boundary, achieved via idempotent writes/transactions; true end-to-end exactly-once across arbitrary external systems is not free
- 2That the network physically never duplicates a packet, so the transport layer guarantees each record is delivered exactly one time to the broker
- 3That messages are never retried by the producer, because retries are the sole cause of duplicates and are disabled entirely under exactly-once mode, so no record can ever be delivered a second time
- 4That consumers must run strictly single-threaded so no two threads can process the same record at once and thereby produce a duplicate side effect or double-count it downstream
Think you can answer under pressure?
Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.