A transit authority continuously publishes ridership pings, vehicle telemetry, and lifecycle events that several analytics services must read at their own pace in order. Which OCI service model fits this pattern?
Select an answer to reveal the explanation.
Short Explanation
Streaming is the city’s continuous event log—buses keep writing; many readers consume at their own pace without erasing the tape. A stream is a partitioned, append-only pub/sub log for continual sequential data such as activity, metrics, and lifecycle events. Queue is the one-shot job inbox; Events targets discrete resource-state changes—not the same tool.
Full Explanation
OCI Streaming provides a partitioned, append-only log of messages. Producers publish; consumers read at their own pace in a publish-subscribe model. It fits workloads where data is produced and processed continually and sequentially—activity feeds, metrics, lifecycle events. It is not OCI Queue’s consume-then-delete job inbox, and it is not OCI Events’ model for discrete resource-state changes. Choose Streaming when durable sequential pub/sub is the requirement.