Bird
Raised Fist0

In an event-driven microservices architecture, how can you ensure reliable event delivery despite service failures?

hard📝 Trade-off Q9 of Q15
LLD - Advanced LLD Concepts
In an event-driven microservices architecture, how can you ensure reliable event delivery despite service failures?
ASend events directly without retries
BUse message brokers with persistent queues and acknowledgments
CStore events only in memory without backup
DIgnore failed events and continue processing
Step-by-Step Solution
Solution:

  1. Step 1: Identify reliability requirements

    Reliable delivery means events must not be lost even if services fail.

  2. Step 2: Choose mechanism for reliability

    Message brokers with persistent queues and acknowledgments ensure events are stored and retried until processed.

  3. Final Answer:

    Use message brokers with persistent queues and acknowledgments -> Option B

  4. Quick Check:

    Persistent queues + ack = reliable delivery [OK]
Quick Trick: Persistent queues and ack ensure no event loss [OK]
Common Mistakes:
MISTAKES
  • Ignoring retries on failure
  • Using volatile in-memory storage
  • Skipping acknowledgments

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More LLD Quizzes
Advanced LLD Concepts - Anti-patterns to avoid - Quiz 4medium Advanced LLD Concepts - Immutability for safety - Quiz 3easy Design — Food Delivery System - Why delivery systems test service coordination - Quiz 4medium Design — Food Delivery System - Rating and review system - Quiz 2easy Design — Hotel Booking System - Room type hierarchy - Quiz 8hard Design — Hotel Booking System - Booking conflict resolution - Quiz 6medium Design — Online Shopping Cart - Product, Cart, Order classes - Quiz 4medium Design — Online Shopping Cart - Product, Cart, Order classes - Quiz 12easy Design — Online Shopping Cart - Pricing strategy (discounts, coupons) - Quiz 14medium Design — Splitwise (Expense Sharing) - Transaction history - Quiz 2easy