Blog

Your dream job? Lets Git IT.
Interactive technical interview preparation platform designed for modern developers.

XGitHub

Platform

  • Categories

Resources

  • Blog
  • About the app
  • FAQ
  • Feedback

Legal

  • Privacy Policy
  • Terms of Service

© 2025 LetsGit.IT. All rights reserved.

LetsGit.IT/Categories/Cloud
Cloudhard

At-least-once vs exactly-once delivery — why do we talk about idempotency?

Tags
#messaging#idempotency#retries
Back to categoryPractice quiz

Answer

With at-least-once delivery, a message can be delivered more than once (retries), so consumers must be idempotent (processing duplicates safely). Exactly-once is hard/expensive in practice, so idempotency is a common solution.

Related questions

MongoDB
MongoDB transaction write conflicts: why do they happen and how should you handle them?
#mongo#transactions#concurrency
Microservices
At-least-once delivery: how do you avoid duplicate side effects in a consumer?
#idempotency#deduplication#messaging
Microservices
What is a retry storm and how do you prevent it?
#retries#backoff#jitter
Databases
How can you make a write idempotent at the database level?
#idempotency#unique-constraint#upsert
Microservices
What is a schema registry and why is it useful for events?
#schema-registry#events#compatibility
Microservices
Why do consumers need to be idempotent in event-driven systems?
#idempotency#messaging#retries