acknowledgement
A reply that confirms a message or delivery was received and safely recorded, so the sender can stop retrying it.
In more detail
Acknowledge only after the message is durably stored or handled, never before, or a crash loses it. An acknowledgement confirms receipt, not that every downstream step has finished.
Example
A Kafka broker acknowledges a produce request once the replicas required by acks have the record.Related terms
- webhook — An HTTP request a provider sends to an address you registered, to tell you an event happened, instead of you polling for it.
- 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.
- at-least-once delivery — A delivery guarantee under which every message arrives, but some may arrive more than once.
- acks — The producer setting that decides how many brokers must confirm a record before the send counts as successful: 0, 1 or all.
- retry — Sending a request again after it failed or timed out, in the hope that it succeeds the second time.
- duplicate record — A second copy of a record that was meant to be written or processed only once.
- visibility timeout — The time a message stays hidden from other consumers after one consumer takes it.
Taught in
- Webhooks Versus Polling — Modern API Architecture: REST, GraphQL & gRPC
- Event-Driven Architecture And Queues — Modern API Architecture: REST, GraphQL & gRPC
- The Payment That Was Charged Twice — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Ninety Minutes, No Question Count — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Acknowledged Is Not Always Safe — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- The Error Storm That Fixes Itself — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- The Retry That Overtook — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- The Setting That Came Back — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Two Brokers Down — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Forty One Under-Replicated Partitions — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- The Data Centre That Went Dark — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Two Controllers At Once — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Seventy One Percent — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- The Night Before The Administrator Exam — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- A Producer In Python — Apache Kafka & Event Streaming
- Acknowledgements: What Acks Means For Durability — Apache Kafka & Event Streaming
- Idempotent Producers And Retries — Apache Kafka & Event Streaming
- Duplicates Are The Default — Apache Kafka & Event Streaming
- Requirements: The Constraints That Shape The System — Scalable System Design & Distributed Architecture
- Queues, Events And Asynchronous Work — Scalable System Design & Distributed Architecture
- The Difference Between A Queue And A Log — Scalable System Design & Distributed Architecture
- Idempotency, And Exactly Once As A Fiction — Scalable System Design & Distributed Architecture
- Worked Design Three: A Metrics Ingestion Pipeline — Scalable System Design & Distributed Architecture
References
- Amazon SQS: What is Amazon SQS?
- Apache Kafka documentation: Message delivery semantics
- Apache Kafka producer configs: acks
- RabbitMQ documentation: Consumer acknowledgements and publisher confirms
- Amazon SQS: Visibility timeout