Which architectural approach best supports a notification system designed for millions of users with customizable delivery channels and ensures fault tolerance?

hard📝 Trade-off Q8 of 15

LLD - Design — Library Management System

ASingle server with multi-threaded notification handlers

BMonolithic application with synchronous notification processing

CMicroservices with event-driven architecture and distributed message queues

DDirect database triggers sending notifications synchronously

Step-by-Step Solution

Solution:

Step 1: Understand scalability needs
Handling millions of users requires scalable, decoupled components.
Step 2: Choose event-driven microservices
Microservices allow independent scaling; event-driven design with distributed queues ensures asynchronous, fault-tolerant delivery.
Final Answer:
Microservices with event-driven architecture and distributed message queues -> Option C
Quick Check:
Event-driven microservices scale and tolerate faults best [OK]

Quick Trick: Use event-driven microservices for scalable, fault-tolerant notifications [OK]

Common Mistakes:

MISTAKES

Using monolithic synchronous processing limits scalability
Relying on single server causes bottlenecks and single point of failure
Database triggers are synchronous and not scalable

Master "Design — Library Management System" in LLD

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Arch Try Challenge Design Recall Scale

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More LLD Quizzes

Which architectural approach best supports a notification system designed for millions of users with customizable delivery channels and ensures fault tolerance?

Step 1: Understand scalability needs

Step 2: Choose event-driven microservices

Final Answer:

Quick Check:

Want More Practice?