A municipal transit dashboard has many producers continually appending vehicle telemetry, and several independent analytics consumers must read—and sometimes replay—the same data with per-partition order and Kafka-shaped clients. Which OCI service should carry that bus?
Select an answer to reveal the explanation.
Short Explanation
When many writers keep appending and many readers need the same ordered history (with replay), you want a stream—not a one-and-done work inbox. Streaming is the Kafka-shaped bus; Queue is for units of work that disappear after success; Events is for OCI’s own resource-state messages.
Full Explanation
OCI Streaming suits continual high-volume appends, independent consumers, per-partition order, and Kafka-compatible clients with replay. Queue is for independently processed transactional messages that should be deleted after success. Events delivers platform-emitted resource changes via rules. Functions are workers you invoke—they are not the durable multi-consumer bus.