Several inspector-app instances must jointly consume a multi-partition work-order stream on OCI Streaming so each partition is handled by only one instance at a time. Which feature coordinates that assignment?
Select an answer to reveal the explanation.
Short Explanation
A consumer group is like assigning each neighborhood’s case pile to one inspector at a time and reshuffling when someone clocks out. Instances in a group coordinate so each partition has one active member; groups rebalance when members join or go silent (roughly thirty seconds without heartbeat/consume). Production multi-partition consumers should use a group; a lone cursor is the simpler single-reader path.
Full Explanation
OCI Streaming consumer groups coordinate member instances so each partition is consumed by one group member at a time. Groups rebalance when instances join or stop heartbeating/consuming for about thirty seconds. Production consumers reading multiple partitions should participate in a consumer group. A lone cursor remains appropriate for simpler single-reader scenarios without group assignment.