ordering guarantee
A promise about whether messages are processed in the order they were sent, which is often limited to one key or partition.
In more detail
Ordering is separate from delivery: an at-least-once queue can still reorder. A design that needs global order should state that cost explicitly.
Related terms
- partition — One of several independent ordered logs a message stream is split into, with each message routed to one partition by its key.
- sequence number — An increasing number attached to each message so the receiver can detect gaps, reorder messages and say where to resume.
- message queue — A store that holds messages from producers until consumers are ready to process them, decoupling the rate of arrival from the rate of work.
- record key — An optional value attached to a record that decides which partition it goes to, so all records with the same key stay together and in order.
- co-location — Placing related records in the same partition, by giving them the same key, so one consumer sees them together and in order.
- max.in.flight.requests.per.connection — The producer setting for how many unacknowledged requests may be outstanding on one broker connection at the same time.
Taught in
- Webhooks Versus Polling — Modern API Architecture: REST, GraphQL & gRPC
- Event-Driven Architecture And Queues — Modern API Architecture: REST, GraphQL & gRPC
- Where A Record Lands — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Topics, Partitions And Where A Record Lands — Apache Kafka & Event Streaming
- Keys And Ordering Per Partition — Apache Kafka & Event Streaming
- Poison Messages And Dead Letter Topics — Apache Kafka & Event Streaming
- Watching Lag And Sizing Partitions — Apache Kafka & Event Streaming