Encapsulation and information hiding in LLD - System Design Guide

Problem Statement

When internal details of a component are exposed, other parts of the system can depend on them directly. This causes bugs when those details change, making the system fragile and hard to maintain.

Solution

Encapsulation bundles data and methods that operate on that data within a single unit, like a class. Information hiding restricts access to internal details, exposing only what is necessary through a controlled interface. This protects the internal state and reduces unintended dependencies.

Architecture

Client

Code

→Encapsulated

↓

This diagram shows a client interacting only with the public methods of an encapsulated component, while internal details remain hidden and protected.

Trade-offs

✓ Pros

→

Reduces system fragility by preventing external code from depending on internal details.

→

Improves maintainability by allowing internal changes without affecting clients.

→

Enhances security by controlling access to sensitive data.

→

Simplifies debugging by localizing effects of changes.

✗ Cons

→

May introduce slight overhead due to access control methods.

→

Requires careful design to decide what to expose and what to hide.

→

Can lead to more boilerplate code for getters/setters if overused.

Always use in object-oriented design, especially when building components or modules that will be reused or maintained by multiple developers.

In very simple scripts or prototypes where speed of development is more important than maintainability and the codebase is small and short-lived.

Real World Examples

Amazon

Amazon uses encapsulation in their microservices to hide internal database schemas and expose only APIs, allowing independent service evolution without breaking clients.

Netflix

Netflix encapsulates streaming session management details within services, exposing only necessary controls to clients, enabling seamless updates without user disruption.

Uber

Uber encapsulates driver location tracking logic inside services, hiding complex algorithms and data structures from other parts of the system.

Code Example

The before code allows direct access to the balance, which can be set to invalid values. The after code hides the balance attribute by making it private and exposes controlled methods to modify it safely, preventing invalid states.

LLD

### Before (no encapsulation, direct access)
class BankAccount:
    def __init__(self, balance):
        self.balance = balance

account = BankAccount(100)
account.balance = -50  # Invalid state allowed


### After (encapsulation and information hiding)
class BankAccount:
    def __init__(self, balance):
        self.__balance = balance  # Private attribute

    def deposit(self, amount):
        if amount > 0:
            self.__balance += amount

    def withdraw(self, amount):
        if 0 < amount <= self.__balance:
            self.__balance -= amount

    def get_balance(self):
        return self.__balance

account = BankAccount(100)
account.deposit(50)
account.withdraw(30)
print(account.get_balance())  # Outputs: 120
account.__balance = -50  # Has no effect on actual balance

Alternatives

Modularization

Modularization groups related functionality into separate modules but does not necessarily hide internal details within those modules.

Use when: When you want to organize code into logical units but do not need strict access control.

Service-Oriented Architecture (SOA)

SOA encapsulates functionality as services with well-defined interfaces but at a higher system level rather than within code units.

Use when: When designing distributed systems requiring loose coupling between large components.

Summary

Encapsulation bundles data and behavior into a single unit and controls access to internal details.

Information hiding protects internal state by exposing only necessary interfaces, reducing dependencies.

Together, they improve maintainability, reduce bugs, and make systems easier to evolve.

Practice

1. What is the main purpose of encapsulation in system design?

easy

A. To hide internal details and protect data from outside access

B. To make all data publicly accessible for easy modification

C. To increase the size of the system components

D. To allow direct access to all internal variables

Solution

1. Step 1: Understand encapsulation concept

   Encapsulation means hiding the internal details of a system or component so that outside code cannot directly access or change them.

2. Step 2: Identify the main goal

   The main goal is to protect data and control how it is accessed or modified, improving security and reducing errors.

3. Final Answer:

   To hide internal details and protect data from outside access -> Option A

4. Quick Check:

   Encapsulation = Hide details and protect data [OK]

Hint: Encapsulation means hiding details, not exposing them [OK]

Common Mistakes:

• Thinking encapsulation means making data public
• Confusing encapsulation with system size
• Believing encapsulation allows direct variable access

2. Which of the following is the correct way to implement encapsulation in a class?

easy

A. Make all variables public and access them directly

B. Avoid using any methods to access data

C. Use private variables and provide public getter and setter methods

D. Use global variables for all data

Solution

1. Step 1: Recall encapsulation implementation

   Encapsulation is done by making variables private so they cannot be accessed directly from outside the class.

2. Step 2: Use public methods for controlled access

   Public getter and setter methods allow controlled reading and updating of private data.

3. Final Answer:

   Use private variables and provide public getter and setter methods -> Option C

4. Quick Check:

   Private variables + public methods = Encapsulation [OK]

Hint: Private variables + public getters/setters = encapsulation [OK]

Common Mistakes:

• Making variables public defeats encapsulation
• Using global variables breaks encapsulation
• Not providing any access methods causes usability issues

3. Consider this code snippet in a system design context:

class Account {
  private balance = 1000;
  public getBalance() { return this.balance; }
  public setBalance(amount) { if(amount >= 0) this.balance = amount; }
}

const acc = new Account();
acc.setBalance(-500);
console.log(acc.getBalance());

What will be the output?

medium

A. -500

B. 1000

C. 0

D. Error

Solution

1. Step 1: Analyze setBalance method behavior

   The method only updates balance if the amount is greater than or equal to zero.

2. Step 2: Check the call with -500

   Since -500 is less than zero, the balance is not updated and remains 1000.

3. Final Answer:

   1000 -> Option B

4. Quick Check:

   Negative amount ignored, balance stays 1000 [OK]

Hint: Setter blocks negative values, so balance stays unchanged [OK]

Common Mistakes:

• Assuming balance changes to -500
• Expecting zero as default
• Thinking code throws an error

4. A developer wrote this code:

class User {
  public name;
  public setName(newName) { this.name = newName; }
}

const user = new User();
user.name = null;
console.log(user.name);

What is the problem related to encapsulation here?

medium

A. The name variable is public and can be set to invalid values directly

B. The setName method is missing

C. The class should not have any variables

D. The console.log statement is incorrect

Solution

1. Step 1: Identify variable access level

   The variable name is public, so it can be changed directly without validation.

2. Step 2: Understand encapsulation violation

   Direct access allows setting invalid values like null, bypassing any checks in setName.

3. Final Answer:

   The name variable is public and can be set to invalid values directly -> Option A

4. Quick Check:

   Public variable allows invalid direct access [OK]

Hint: Public variables can be changed without checks, breaking encapsulation [OK]

Common Mistakes:

• Thinking setName method is missing
• Believing variables should be removed
• Blaming console.log for output

5. You are designing a banking system where account balance must never be negative. Which approach best uses encapsulation and information hiding to enforce this rule?

hard

A. Make balance public and rely on users to not set negative values

B. Store balance as a global variable accessible everywhere

C. Do not provide any methods to access balance

D. Make balance private and provide a setter that only updates if amount ≥ 0

Solution

1. Step 1: Protect balance data

   Making balance private hides it from direct external changes, preventing accidental or malicious updates.

2. Step 2: Control updates via setter method

   The setter method enforces the rule by allowing updates only if the new amount is zero or positive.

3. Step 3: Avoid unsafe alternatives

   Public or global variables allow uncontrolled changes, risking negative balances and errors.

4. Final Answer:

   Make balance private and provide a setter that only updates if amount ≥ 0 -> Option D

5. Quick Check:

   Private balance + validated setter = safe encapsulation [OK]

Hint: Private data + validated setter enforces rules safely [OK]

Common Mistakes:

• Making balance public and trusting users
• Not providing access methods causes usability issues
• Using global variables breaks encapsulation