Adding a little bit more on the subject of consumer delivery guarantees (#5390)

Signed-off-by: Matthias Wessendorf <mwessend@redhat.com>

Signed-off-by: Matthias Wessendorf <mwessend@redhat.com>
This commit is contained in:
Matthias Wessendorf 2023-01-24 19:09:39 +01:00 committed by GitHub
parent 3132270389
commit fb4e05a482
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions

View File

@ -381,10 +381,10 @@ spec:
The supported consumer delivery guarantees are:
* `unordered`: An unordered consumer is a non-blocking consumer that delivers messages unordered, while preserving proper offset management.
* `ordered`: An ordered consumer is a per-partition blocking consumer that waits for a successful response from the CloudEvent subscriber before it delivers the next message of the partition.
* `unordered`: An unordered consumer is a non-blocking consumer that delivers messages unordered, while preserving proper offset management. Useful when there is a high demand of parallel consumption and no need for explicit ordering. One example could be processing of click analytics.
* `ordered`: An ordered consumer is a per-partition blocking consumer that waits for a successful response from the CloudEvent subscriber before it delivers the next message of the partition. Useful when there is a need for more strict ordering or if there is a relationship or grouping between events. One example could be processing of customer orders.
`unordered` is the default ordering guarantee.
The `unordered` delivery is the default ordering guarantee.
### Additional information