Null Object pattern in LLD - Architecture Diagram

System Overview - Null Object pattern

The Null Object pattern provides a default object that represents a "do nothing" or "empty" behavior instead of using null references. This helps avoid null checks and simplifies code by ensuring that all objects respond to the same methods safely.

Key requirements include seamless substitution of null objects, consistent interface implementation, and preventing null pointer errors.

Architecture Diagram

User
  |
  v
Client Code
  |
  v
+-------------------+
| Abstract Interface |
+-------------------+
    /           \
   /             \
Real Object    Null Object
(Service)     (Do Nothing)
    |               |
    v               v
  Business       Empty Behavior
  Logic          Implementation

Components

User

actor

Initiates requests that require service objects

Client Code

component

Uses objects through a common interface without null checks

Abstract Interface

interface

Defines common methods for real and null objects

Real Object

service

Implements actual business logic

Null Object

service

Implements empty behavior to avoid null checks

Request Flow - 5 Hops

User → Client Code

Client Code → Abstract Interface

Client Code → Real Object or Null Object

Real Object or Null Object → Client Code

Client Code → User

Failure Scenario

Component Fails:Null Object

Impact:If Null Object is missing or incorrectly implemented, client code may encounter null pointer errors or require explicit null checks.

Mitigation:Ensure Null Object fully implements the interface with safe default behavior to prevent null checks and errors.

Architecture Quiz - 3 Questions

What is the main purpose of the Null Object in this pattern?

A To provide a default do-nothing implementation to avoid null checks

B To replace the real object with a faster version

C To handle database connections

D To log errors when null values occur

Design Principle

The Null Object pattern simplifies client code by providing a safe default object that implements the expected interface, eliminating the need for null checks and reducing errors.

Practice

1. What is the main purpose of the Null Object pattern in system design?

easy

A. To encrypt sensitive data before storage

B. To create multiple instances of an object for load balancing

C. To optimize database queries by caching null values

D. To replace null references with an object that does nothing but follows the expected interface

Solution

1. Step 1: Understand the problem with null references

   Null references can cause errors like null pointer exceptions when methods are called on them.

2. Step 2: Explain how Null Object pattern solves this

   The pattern replaces null with a harmless object that implements the same interface but performs no action, avoiding errors.

3. Final Answer:

   To replace null references with an object that does nothing but follows the expected interface -> Option D

4. Quick Check:

   Null Object pattern = harmless object instead of null [OK]

Hint: Null Object means safe empty object, not null itself [OK]

Common Mistakes:

• Confusing Null Object with caching or encryption
• Thinking it creates multiple instances for load balancing
• Assuming it optimizes database queries

2. Which of the following is the correct way to implement a Null Object in a class hierarchy?

easy

A. Create a subclass that overrides methods with empty implementations

B. Use a global variable set to null

C. Throw exceptions in the Null Object methods

D. Return null from all methods in the Null Object

Solution

1. Step 1: Identify how Null Object should behave

   It should implement the same interface but provide harmless (empty) behavior.

2. Step 2: Choose the correct implementation approach

   Creating a subclass that overrides methods with empty implementations fits the pattern.

3. Final Answer:

   Create a subclass that overrides methods with empty implementations -> Option A

4. Quick Check:

   Null Object subclass overrides methods safely [OK]

Hint: Null Object overrides methods with empty bodies [OK]

Common Mistakes:

• Using null variables instead of objects
• Throwing exceptions defeats Null Object purpose
• Returning null causes errors again

3. Consider this code snippet using Null Object pattern:

class Logger {
  log(message) { console.log(message); }
}

class NullLogger {
  log(message) { /* do nothing */ }
}

function process(data, logger) {
  logger.log('Start');
  // process data
  logger.log('End');
}

const logger = new NullLogger();
process('input', logger);

What will be the output when this code runs?

medium

A. Logs 'Start' and 'End' messages to console

B. No output will be printed

C. Throws an error because NullLogger does not log

D. Logs only 'Start' message

Solution

1. Step 1: Analyze NullLogger behavior

   NullLogger's log method does nothing, so no console output occurs.

2. Step 2: Trace process function calls

   process calls logger.log twice, but since logger is NullLogger, no output is printed.

3. Final Answer:

   No output will be printed -> Option B

4. Quick Check:

   NullLogger logs nothing = no output [OK]

Hint: Null Object methods do nothing, so no output [OK]

Common Mistakes:

• Assuming NullLogger logs messages
• Expecting errors from NullLogger
• Thinking partial logs appear

4. You have a Null Object implementation but still get null pointer exceptions in your system. What is the most likely cause?

medium

A. Some parts of the code still use null instead of the Null Object

B. The Null Object throws exceptions intentionally

C. The Null Object does not implement the required interface

D. The Null Object caches null values incorrectly

Solution

1. Step 1: Understand Null Object pattern goal

   It replaces null references to avoid null pointer exceptions.

2. Step 2: Identify why exceptions still occur

   If some code still uses null directly, exceptions will happen despite Null Object presence.

3. Final Answer:

   Some parts of the code still use null instead of the Null Object -> Option A

4. Quick Check:

   Null Object must replace all nulls to avoid exceptions [OK]

Hint: All nulls must be replaced by Null Object [OK]

Common Mistakes:

• Assuming Null Object throws exceptions
• Ignoring interface implementation correctness
• Confusing caching with Null Object usage

5. In a large-scale system, how does using the Null Object pattern improve system design and scalability?

hard

A. It requires complex synchronization, making the system slower

B. It increases memory usage by creating many null objects, reducing performance

C. It reduces conditional checks and prevents null-related errors, simplifying code and improving reliability

D. It replaces all objects with nulls to save resources

Solution

1. Step 1: Identify benefits of Null Object in large systems

   By replacing nulls, it removes many if-null checks and prevents errors, making code cleaner.

2. Step 2: Understand impact on scalability and reliability

   Simpler code with fewer errors means easier maintenance and better system stability at scale.

3. Final Answer:

   It reduces conditional checks and prevents null-related errors, simplifying code and improving reliability -> Option C

4. Quick Check:

   Null Object simplifies code and boosts reliability [OK]

Hint: Null Object reduces checks, improves reliability [OK]

Common Mistakes:

• Thinking Null Object wastes memory excessively
• Assuming it slows system due to synchronization
• Believing it replaces all objects with nulls