Notification on state change in LLD - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a 'Notification on state change' in system design?

It is a mechanism where a system alerts interested components or users whenever a specific state or condition changes, ensuring timely updates and reactions.

beginner

Name two common patterns used to implement notifications on state changes.

Observer pattern and Publish-Subscribe pattern are commonly used to notify components about state changes.

intermediate

Why is decoupling important in notification systems for state changes?

Decoupling allows the notifier and the receiver to operate independently, making the system more flexible, scalable, and easier to maintain.

intermediate

What role does an event bus or message broker play in state change notifications?

It acts as a middleman that receives state change events and distributes them to all interested subscribers efficiently and reliably.

advanced

How can you ensure notifications on state changes are scalable in a large system?

By using asynchronous messaging, load balancing, and partitioning events, the system can handle many notifications without slowing down.

Which pattern is best suited for notifying multiple components about a state change?

A Observer pattern

B Singleton pattern

C Factory pattern

D Decorator pattern

The Observer pattern allows multiple components to listen and react to state changes.

What is a key benefit of using a message broker for notifications?

A Hardcoded notification logic

B Synchronous blocking calls

C Direct coupling between sender and receiver

D Decoupling and asynchronous communication

Message brokers enable decoupled and asynchronous communication between components.

Which of the following is NOT a good practice for scalable notification systems?

A Load balancing notification delivery

B Sending notifications synchronously in the main thread

C Using asynchronous messaging

D Partitioning events by type or source

Synchronous notification in the main thread can block and reduce scalability.

In a notification system, what does decoupling help achieve?

A Independent evolution of sender and receiver

B Increased system complexity

C Tight integration of components

D Direct method calls between components

Decoupling allows sender and receiver to change independently without affecting each other.

What is the main role of an event bus in state change notifications?

A Store data permanently

B Generate new events

C Route events to interested subscribers

D Encrypt messages

An event bus routes state change events to all subscribers who want to receive them.

Explain how you would design a notification system for state changes in a simple application.

Think about how components can listen and react without tight connections.

Describe strategies to ensure notifications on state changes remain scalable as the system grows.

Focus on handling many notifications efficiently.

Practice

1. What is the main purpose of a notification system on state change in software design?

easy

A. To inform interested components immediately when data changes

B. To store data permanently in a database

C. To increase the size of the application

D. To delay updates until the user refreshes manually

Solution

1. Step 1: Understand the role of notifications

   Notifications alert parts of a system or users when something important changes.

2. Step 2: Identify the purpose of state change notifications

   They ensure components get updates immediately without waiting or manual refresh.

3. Final Answer:

   To inform interested components immediately when data changes -> Option A

4. Quick Check:

   Notification = Immediate update [OK]

Hint: Notifications alert on change, not store or delay [OK]

Common Mistakes:

• Confusing notification with data storage
• Thinking notifications delay updates
• Assuming notifications increase app size

2. Which of the following is the correct method name to notify observers in a typical observer pattern implementation?

easy

A. unsubscribe()

B. updateState()

C. subscribe()

D. notifyObservers()

Solution

1. Step 1: Recall observer pattern methods

   Common methods include subscribe, unsubscribe, and notifyObservers.

2. Step 2: Identify the method that sends updates

   notifyObservers() is used to alert all subscribed observers about changes.

3. Final Answer:

   notifyObservers() -> Option D

4. Quick Check:

   Notify method = notifyObservers() [OK]

Hint: Notify method usually named notifyObservers() [OK]

Common Mistakes:

• Confusing subscribe with notify
• Using updateState() which changes state, not notify
• Mixing unsubscribe with notification

3. Consider this simplified code snippet for a notification system:

class Subject:
    def __init__(self):
        self.observers = []
    def subscribe(self, observer):
        self.observers.append(observer)
    def notify(self, message):
        for obs in self.observers:
            obs.update(message)

class Observer:
    def update(self, message):
        print(f"Received: {message}")

subject = Subject()
obs1 = Observer()
subject.subscribe(obs1)
subject.notify("State changed")

What will be the output when subject.notify("State changed") is called?

medium

A. Error: update method missing

B. No output

C. Received: State changed

D. Received: None

Solution

1. Step 1: Trace subscription and notification

   Observer obs1 is subscribed to subject, so it is in the observers list.

2. Step 2: Check notify method behavior

   notify calls update on each observer with the message "State changed".

3. Final Answer:

   Received: State changed -> Option C

4. Quick Check:

   Observer prints message on notify [OK]

Hint: Subscribed observers receive and print messages [OK]

Common Mistakes:

• Assuming notify does nothing without explicit call
• Thinking update method is missing
• Expecting no output if observers list is empty

4. In the following code, what is the main issue that prevents observers from receiving notifications?

class Subject:
    def __init__(self):
        self.observers = set()
    def subscribe(self, observer):
        self.observers.add(observer)
    def notify(self, message):
        for obs in self.observers:
            obs.receive(message)

class Observer:
    def update(self, message):
        print(f"Got: {message}")

subject = Subject()
obs1 = Observer()
subject.subscribe(obs1)
subject.notify("Update")

medium

A. Observers are stored in a set instead of a list

B. Method notify calls obs.receive but Observer has update method

C. subscribe method uses add instead of append

D. Observer class is missing

Solution

1. Step 1: Check method called in notify

   notify() calls obs.receive(message).

2. Step 2: Check Observer class methods

   Observer defines update(message), but no receive() method.

3. Final Answer:

   Method notify calls obs.receive but Observer has update method -> Option B

4. Quick Check:

   Method name mismatch causes AttributeError [OK]

Hint: Check method names called vs defined in observers [OK]

Common Mistakes:

• Confusing set vs list for storing observers
• Ignoring method name mismatches
• Assuming missing class when it exists

5. You are designing a scalable notification system for state changes in a distributed application. Which design choice best supports efficient notifications to thousands of subscribers without blocking the main process?

hard

A. Use asynchronous message queues to dispatch notifications

B. Notify all subscribers synchronously in a loop

C. Store notifications in a database and poll subscribers

D. Send notifications only when the system restarts

Solution

1. Step 1: Understand scalability needs

   Thousands of subscribers require non-blocking, efficient notification delivery.

2. Step 2: Evaluate design options

   Synchronous loops block main process; polling adds delay; restart notifications are impractical.

3. Step 3: Identify best practice

   Asynchronous message queues decouple notification sending, allowing scalable, fast delivery.

4. Final Answer:

   Use asynchronous message queues to dispatch notifications -> Option A

5. Quick Check:

   Async queues = scalable notifications [OK]

Hint: Async queues handle many subscribers efficiently [OK]

Common Mistakes:

• Using synchronous loops causing delays
• Relying on polling which is slow
• Sending notifications only on restart