Streetlight controllers publish events to OCI Streaming. A flaky consumer may see the same message again after a failed commit, and another team may replay within the retention window after a bug fix. What delivery and retention behavior should handlers assume?
Select an answer to reveal the explanation.
Short Explanation
Streaming hands you the letter at least once and keeps a copy in the mailroom until the retention window expires—so open every letter as if it might arrive twice. Failed commits can redeliver; another consumer can replay while data is retained. There is no Queue-style delete-on-ack. Design handlers to be idempotent.
Full Explanation
OCI Streaming delivers each message at least once; a consumer that fails to commit progress can receive the message again. Messages remain available until the stream’s retention window ends, enabling replay by the same or another consumer. Unlike OCI Queue, there is no delete-on-acknowledgment requirement. Application handlers must be idempotent to tolerate redelivery and replay within retention.