A civic apps team debates where to put continuous click-stream telemetry versus reactions to OCI bucket and database state changes. Which distinction correctly separates Events from Streaming?
Select an answer to reveal the explanation.
Short Explanation
Events is for discrete OCI-emitted state changes you filter with rules. Streaming is the continuous bus you publish to, with partitions and replay. Click-streams belong on Streaming; bucket emits belong on Events—not the other way around.
Full Explanation
OCI Events subscribes to platform-emitted resource changes through rules. OCI Streaming is an application-managed append log with partitions, offsets, and consumer replay. Putting click-streams on Events rules is the wrong shape; waiting for a bucket emit by polling a stream you never wrote to is also wrong. Enable Object Storage emit for Events—it does not make Streaming a substitute for rules.