Interface Segregation Principle in LLD - Scalability & System Analysis

Scalability Analysis - Interface Segregation Principle

Growth Table: Interface Segregation Principle

Users / Scale	Interface Complexity	System Maintainability	Development Speed	Code Coupling
100 users	Few interfaces, some large ones	Manageable with small team	Fast initial development	Moderate coupling
10,000 users	Interfaces start to grow, some too broad	Maintenance slows due to interface bloat	Development slows due to unclear contracts	Increased coupling, harder to change
1,000,000 users	Many clients affected by large interfaces	High risk of bugs from interface changes	Slow development, frequent regressions	Strong coupling, poor modularity
100,000,000 users	Interfaces become a major bottleneck	System fragile, costly to maintain	Very slow development, high error rate	Very tight coupling, hard to scale teams

First Bottleneck

The first bottleneck is the interface design itself. When interfaces are too broad or force clients to depend on methods they don't use, it causes tight coupling. This leads to slower development, more bugs, and difficulty in scaling teams and features. As user base and features grow, this coupling becomes a major blocker.

Scaling Solutions

• Split large interfaces into smaller, client-specific ones to reduce unnecessary dependencies.
• Apply Interface Segregation Principle (ISP) strictly to keep interfaces focused and minimal.
• Use composition over inheritance to build flexible systems.
• Automate interface contracts with tools to ensure clients only depend on needed methods.
• Modularize codebase so teams can work independently on separate interfaces.

Back-of-Envelope Cost Analysis

• At 1,000 QPS, broad interfaces cause frequent code changes affecting many clients, increasing bug fix time by ~30%.
• At 10,000 QPS, maintenance overhead grows, requiring ~20% more developer time to manage interface-related bugs.
• At 1M QPS, tight coupling can cause deployment delays, costing thousands in downtime and developer hours.
• Bandwidth and storage are less impacted directly, but developer productivity and system reliability suffer greatly.

Interview Tip

When discussing scalability of interface design, start by explaining how broad interfaces cause tight coupling and slow development. Then describe how splitting interfaces improves modularity and team independence. Finally, mention how this reduces bugs and speeds up feature delivery as the system grows.

Self Check

Your database handles 1000 QPS. Traffic grows 10x. What do you do first?

Answer: For interface design, first check if clients depend on large, broad interfaces causing tight coupling. Begin splitting interfaces into smaller, focused ones to reduce dependencies and improve maintainability as traffic and features grow.

Key Result

Broad interfaces cause tight coupling that slows development and increases bugs as users grow; splitting interfaces per the Interface Segregation Principle improves modularity and scalability.

Practice

1. What is the main idea behind the Interface Segregation Principle in system design?

easy

A. Interfaces should be as large as possible to cover all features.

B. All classes must implement every method of an interface.

C. Clients should only depend on methods they actually use.

D. Interfaces should be avoided to reduce complexity.

Solution

1. Step 1: Understand the principle's goal

   The Interface Segregation Principle aims to keep interfaces small and focused so clients are not forced to depend on unused methods.

2. Step 2: Match the correct description

   Clients should only depend on methods they actually use. correctly states that clients should only depend on methods they use, which aligns with the principle.

3. Final Answer:

   Clients should only depend on methods they actually use. -> Option C

4. Quick Check:

   Interface Segregation Principle = Clients depend only on used methods [OK]

Hint: Focus on clients using only needed methods [OK]

Common Mistakes:

• Thinking interfaces must be large and cover all features
• Believing all classes must implement every interface method
• Assuming interfaces should be avoided

2. Which of the following interface definitions follows the Interface Segregation Principle?

easy

A. interface Printer { void print(); void scan(); void fax(); }

B. interface Machine { void doEverything(); }

C. interface Device { void operate(); void print(); void scan(); void fax(); }

D. interface Printer { void print(); } interface Scanner { void scan(); }

Solution

1. Step 1: Analyze interface sizes

   interface Printer { void print(); } interface Scanner { void scan(); } splits responsibilities into separate interfaces for printing and scanning, keeping them focused and small.

2. Step 2: Compare with other options

   Options A, B, and C combine multiple unrelated methods into one interface, violating the principle.

3. Final Answer:

   Separate interfaces for each responsibility -> Option D

4. Quick Check:

   Small focused interfaces = interface Printer { void print(); } interface Scanner { void scan(); } [OK]

Hint: Look for interfaces with single focused responsibility [OK]

Common Mistakes:

• Choosing interfaces with many unrelated methods
• Ignoring separation of concerns
• Confusing interface segregation with inheritance

3. Given these interfaces and classes, what will be the output?

interface Printer { void print(); }
interface Scanner { void scan(); }
class MultiFunctionDevice implements Printer, Scanner {
  public void print() { System.out.println("Printing document"); }
  public void scan() { System.out.println("Scanning document"); }
}

MultiFunctionDevice device = new MultiFunctionDevice();
device.print();
device.scan();

medium

A. Printing document\nScanning document

B. Printing document

C. Scanning document

D. Compilation error

Solution

1. Step 1: Understand class implementation

   The class implements both Printer and Scanner interfaces and provides both methods.

2. Step 2: Trace method calls

   Calling device.print() prints "Printing document" and device.scan() prints "Scanning document".

3. Final Answer:

   Printing document\nScanning document -> Option A

4. Quick Check:

   Both methods print messages = Printing document\nScanning document [OK]

Hint: Check which interfaces are implemented and methods called [OK]

Common Mistakes:

• Assuming only one method runs
• Expecting compilation error due to multiple interfaces
• Confusing method outputs

4. Identify the problem in this interface design violating the Interface Segregation Principle:

interface Worker {
  void work();
  void eat();
}

class Robot implements Worker {
  public void work() { System.out.println("Robot working"); }
  public void eat() { throw new UnsupportedOperationException(); }
}

medium

A. Worker interface is too broad, forcing Robot to implement unused methods.

B. Robot should implement eat() properly.

C. Robot class should not implement Worker interface.

D. No problem, this design is correct.

Solution

1. Step 1: Analyze interface methods

   The Worker interface combines work and eat methods, but Robot cannot eat.

2. Step 2: Identify violation

   Robot is forced to implement eat() which it does not support, violating Interface Segregation Principle.

3. Final Answer:

   Worker interface is too broad, forcing Robot to implement unused methods. -> Option A

4. Quick Check:

   Broad interface forcing unused methods = Worker interface is too broad, forcing Robot to implement unused methods. [OK]

Hint: Check if all interface methods apply to all implementers [OK]

Common Mistakes:

• Thinking Robot must implement eat() properly
• Believing no problem exists
• Suggesting Robot should avoid interface

5. You are designing a payment system with interfaces for different payment methods. Which design best follows the Interface Segregation Principle?

hard

A. interface Payment { void payWithCard(); void payWithCash(); void payWithCrypto(); }

B. interface CardPayment { void payWithCard(); } interface CashPayment { void payWithCash(); } interface CryptoPayment { void payWithCrypto(); }

C. interface Payment { void pay(); } class AllPayments implements Payment { void pay() { /* all methods */ } }

D. interface Payment { void payWithCard(); void payWithCash(); } class CryptoPayment implements Payment { void payWithCard() {} void payWithCash() {} }

Solution

1. Step 1: Evaluate interface segregation

   interface CardPayment { void payWithCard(); } interface CashPayment { void payWithCash(); } interface CryptoPayment { void payWithCrypto(); } splits payment methods into separate interfaces, allowing clients to implement only what they need.

2. Step 2: Compare other options

   Options A, B, and D force clients to implement methods they may not use, violating the principle.

3. Final Answer:

   Separate interfaces for each payment method -> Option B

4. Quick Check:

   Separate interfaces = interface CardPayment { void payWithCard(); } interface CashPayment { void payWithCash(); } interface CryptoPayment { void payWithCrypto(); } [OK]

Hint: Split interfaces by payment method for flexibility [OK]

Common Mistakes:

• Combining all payment methods in one interface
• Forcing classes to implement unused methods
• Ignoring interface segregation benefits