Null Object pattern in LLD - System Design Exercise

Design: Null Object Pattern Implementation

Design the pattern structure and usage in a system to replace null references with Null Objects. Out of scope are specific language implementations or integration with large frameworks.

Functional Requirements

FR1: Provide a way to avoid null checks in client code when dealing with absent or missing objects

FR2: Ensure the system can handle operations on objects that may be null without throwing errors

FR3: Allow seamless substitution of a 'null object' that behaves like a real object but does nothing

FR4: Support easy extension to add new types of null objects for different classes

Non-Functional Requirements

NFR1: The pattern should not introduce significant performance overhead

NFR2: The design must be simple and easy to understand for developers

NFR3: The solution should be language-agnostic and applicable in low-level design

NFR4: Must maintain code readability and reduce conditional branching

Think Before You Design

Questions to Ask

❓ Question 1

❓ Question 2

❓ Question 3

❓ Question 4

❓ Question 5

Key Components

Abstract base class or interface defining common methods

Concrete real object classes implementing the interface

Null Object class implementing the interface with empty or default behavior

Client code that uses the interface without null checks

Design Patterns

Polymorphism to substitute Null Object for null references

Factory pattern to create real or null objects transparently

Dependency Injection to provide Null Objects where needed

Strategy pattern if behavior varies between real and null objects

Reference Architecture

Interface

↓

RealObject

Components

Interface

Abstract class or interface

Defines common methods for real and null objects

RealObject

Concrete class

Implements actual behavior for the interface

NullObject

Concrete class

Implements interface with empty or default behavior to avoid null checks

Client

Any

Uses the interface without null checks, relying on polymorphism

Request Flow

1. Client requests an object from a factory or service.

2. Factory returns either a RealObject or a NullObject implementing the interface.

3. Client calls methods on the returned object without checking for null.

4. If the object is RealObject, real behavior executes.

5. If the object is NullObject, safe default behavior executes (e.g., no operation).

6. Client continues without null pointer exceptions or conditional checks.

Database Schema

Not applicable for Null Object pattern as it is a design pattern focused on object behavior rather than data storage.

Scaling Discussion

Bottlenecks

Increased number of NullObject classes if many interfaces require null handling

Potential confusion if NullObject behavior is not clearly documented

Performance overhead if NullObject methods do unnecessary work

Difficulty in debugging when NullObject silently swallows operations

Solutions

Use generic NullObject implementations where possible to reduce class count

Document NullObject behavior clearly for developers

Keep NullObject methods minimal and efficient

Add logging or monitoring in NullObject methods to trace usage if needed

Interview Tips

Time: Spend 5 minutes explaining the problem of null references, 10 minutes describing the Null Object pattern structure and benefits, 5 minutes walking through a simple example, and 5 minutes discussing trade-offs and scaling.

Explain how Null Object pattern eliminates null checks and reduces errors

Describe the role of interface and polymorphism in the pattern

Show how client code becomes simpler and safer

Discuss when to use Null Object vs other approaches like Optional or exceptions

Mention potential pitfalls and how to mitigate them

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