replay
Delivering or returning something again: a stored result for a repeated request, or past events for a client that missed them.
In more detail
An idempotency key makes a retried create a safe replay of the first result. Webhook and event systems offer replay or catch-up so receivers can recover missed deliveries after downtime. Replay must stay within the caller’s own data.
Example
In Kafka you replay by consuming from an earlier offset or starting a new consumer group from the earliest offset.Related terms
- idempotency key — A unique value a client sends with a non-idempotent request, such as a create, so the server can recognise a retry and return the original result instead of acting twice.
- webhook — An HTTP request a provider sends to an address you registered, to tell you an event happened, instead of you polling for it.
- Last-Event-ID — The header a Server-Sent Events client sends when reconnecting, carrying the id of the last event it received so the server can continue from there.
- dead letter queue — A separate queue where messages that keep failing are moved, so they stop blocking others and can be inspected and replayed later.
- append-only log — A data structure where new entries are only ever added at the end and existing entries are never changed in place.
- offset — The permanent position number of a record inside its partition, starting at zero and increasing by one for each record.
- retention — How long data such as backups, logs or snapshots is kept before it is deleted.
- projection — A copy of data reshaped for one purpose, such as a search index or cache, built from the source of truth.
- auto.offset.reset — The consumer setting that decides where to start reading when a group has no committed offset: earliest or latest.
- materialised view — A stored table of results computed from other data, kept so queries do not have to recompute them.
- idempotency — The property of an operation that gives the same result whether you run it once or many times, because a repeat run finds nothing left to do.
Taught in
- Idempotency Keys — Modern API Architecture: REST, GraphQL & gRPC
- Webhooks Versus Polling — Modern API Architecture: REST, GraphQL & gRPC
- Server-Sent Events — Modern API Architecture: REST, GraphQL & gRPC
- The Night Larder Could Not Buy Servers Fast Enough — AWS Certified Cloud Practitioner (CLF-C02) Exam Prep
- Ninety Minutes, Sixty Five Questions — AWS Certified Cloud Practitioner (CLF-C02) Exam Prep
- Cloud Concepts Sprint: Twelve Cards — AWS Certified Cloud Practitioner (CLF-C02) Exam Prep
- Which Zone, Which Journey? — AWS Certified Cloud Practitioner (CLF-C02) Exam Prep
- Four Hundred Missing Labels — AWS Certified Cloud Practitioner (CLF-C02) Exam Prep
- Forty Eight Of Sixty Five — AWS Certified Cloud Practitioner (CLF-C02) Exam Prep
- The Morning An Availability Zone Went Dark — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Who Signs In: Identity Center, STS And Cognito — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Decoupling: SQS, SNS, EventBridge And Step Functions — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Load Balancers And Auto Scaling: Capacity That Arrives On Time — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Databases That Survive: Standbys, Replicas And Global Tables — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Ingest And Transform: Streams, Lakes And Partitions — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Cost Governance: Tags, Budgets And Reports That Speak Up — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- The Payment That Was Charged Twice — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- The Queue That Forgot — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Replay Everything Since Eleven — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Forty Minutes To Count Again — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- A Sink That Died On Record Nine — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Why A Log And Not A Queue — Apache Kafka & Event Streaming
- Duplicates Are The Default — Apache Kafka & Event Streaming
- Poison Messages And Dead Letter Topics — Apache Kafka & Event Streaming
- Materialised Views From A Stream — Apache Kafka & Event Streaming
- When Kafka Is The Wrong Tool — Apache Kafka & Event Streaming
- The Storage Decision: Relational Versus Document — Scalable System Design & Distributed Architecture
- The Storage Decision: Key Value, Search And Blob — Scalable System Design & Distributed Architecture
- Replication, Failover And Leader Election — Scalable System Design & Distributed Architecture
- Eventual Consistency And What It Costs A Product — Scalable System Design & Distributed Architecture
- The Difference Between A Queue And A Log — Scalable System Design & Distributed Architecture
- Worked Design Two: Scaling Chat Fan Out — Scalable System Design & Distributed Architecture
- Worked Design Three: A Metrics Ingestion Pipeline — Scalable System Design & Distributed Architecture
References
- IETF draft: The Idempotency-Key HTTP header field
- GitHub Docs: Best practices for using webhooks
- Apache Kafka documentation: Design
- Apache Kafka design: consumer position