Why Program to interface not implementation in LLD? - Purpose & Use Cases

The Big Idea

What if you could change parts of your system without breaking everything else?

The Scenario

Imagine building a complex machine where every part is tightly connected to a specific brand and model. If one part breaks or you want to upgrade, you must redesign the whole machine from scratch.

The Problem

This tight connection makes changes slow and risky. Fixing one part can break others. It's hard to test or replace pieces independently. The system becomes fragile and costly to maintain.

The Solution

By programming to an interface, you only depend on what a part should do, not how it does it. This lets you swap parts easily, test components separately, and build flexible, robust systems that adapt to change.

Before vs After

✗ Before

Car car = new TeslaModelS();
car.drive();

✓ After

Car car = new ElectricCar();
car.drive();

What It Enables

This approach unlocks easy upgrades, better testing, and systems that grow without breaking.

Real Life Example

Think of a smartphone charger: any charger with the right plug fits any phone. You don't need a charger from the phone's brand to power it.

Key Takeaways

Reduces tight coupling between parts.

Makes systems easier to change and maintain.

Supports flexible and testable designs.

Practice

1. What is the main benefit of programming to an interface rather than a concrete implementation?

easy

A. It allows changing the implementation without affecting the code that uses it.

B. It makes the program run faster by using direct calls.

C. It reduces the number of lines of code needed.

D. It forces the use of only one implementation.

Solution

1. Step 1: Understand interface vs implementation

   Programming to an interface means using a contract that defines what methods are available, not how they work internally.

2. Step 2: Identify the benefit of this approach

   This allows swapping or changing the underlying implementation without changing the code that depends on the interface.

3. Final Answer:

   It allows changing the implementation without affecting the code that uses it. -> Option A

4. Quick Check:

   Interface abstraction = flexibility [OK]

Hint: Interfaces hide details, so implementations can change freely [OK]

Common Mistakes:

• Thinking it improves speed directly
• Believing it reduces code size automatically
• Assuming only one implementation is allowed

2. Which of the following code snippets correctly shows programming to an interface in a language like Java?

easy

A. List<String> list = new ArrayList<>();

B. ArrayList<String> list = new ArrayList<>();

C. List<String> list = new List<>();

D. ArrayList<String> list = new List<>();

Solution

1. Step 1: Identify interface and implementation

   In Java, List is an interface, and ArrayList is a concrete class implementing List.

2. Step 2: Check which declaration uses interface type

   Declaring the variable as List and instantiating with ArrayList means programming to interface, not implementation.

3. Final Answer:

   List<String> list = new ArrayList<>(); -> Option A

4. Quick Check:

   Variable type = interface [OK]

Hint: Use interface type on left side, implementation on right [OK]

Common Mistakes:

• Using concrete class on both sides
• Trying to instantiate an interface directly
• Mixing types incorrectly

3. Given the following code in a language supporting interfaces:

interface Vehicle { void drive(); }
class Car implements Vehicle { public void drive() { print("Car driving"); } }
class Bike implements Vehicle { public void drive() { print("Bike driving"); } }
Vehicle v = new Car();
v.drive();

What will be the output?

medium

A. Compilation error

B. Bike driving

C. Car driving

D. Vehicle driving

Solution

1. Step 1: Identify the object type assigned to interface variable

   The variable v of type Vehicle is assigned a new Car object.

2. Step 2: Determine which drive() method runs

   Calling v.drive() runs the Car's drive() method because the actual object is Car.

3. Final Answer:

   Car driving -> Option C

4. Quick Check:

   Interface variable calls actual object's method [OK]

Hint: Interface calls use actual object's method at runtime [OK]

Common Mistakes:

• Assuming interface method runs
• Confusing object type with variable type
• Expecting compilation error due to interface

4. Consider this code snippet:

interface Printer { void print(); }
class LaserPrinter implements Printer { void print() { System.out.println("Laser printing"); } }
Printer p = new LaserPrinter();
p.print();

Why does this code cause a compilation error?

medium

A. Interfaces cannot be instantiated.

B. LaserPrinter does not implement print() method.

C. Printer cannot be used as a variable type.

D. The print() method in LaserPrinter is not declared public.

Solution

1. Step 1: Check method visibility in implementation

   Interface methods are public by default, so implementing methods must be public.

2. Step 2: Identify method declaration in LaserPrinter

   LaserPrinter's print() method lacks the public modifier, causing a visibility mismatch error.

3. Final Answer:

   The print() method in LaserPrinter is not declared public. -> Option D

4. Quick Check:

   Interface methods require public implementation [OK]

Hint: Implement interface methods as public to avoid errors [OK]

Common Mistakes:

• Thinking interfaces can't be variable types
• Believing missing method causes error instead
• Ignoring method visibility rules

5. You are designing a payment system where multiple payment methods (CreditCard, PayPal, Crypto) can be used. To follow the principle 'Program to interface not implementation', which design is best?

hard

A. Write separate classes with no common interface and call their methods directly.

B. Create a PaymentMethod interface with a pay() method, and implement it in each payment class.

C. Use a single PaymentProcessor class with if-else to handle all payment types.

D. Make all payment classes inherit from a concrete PaymentProcessor class.

Solution

1. Step 1: Identify the need for abstraction

   Multiple payment types require a common contract to allow flexible usage.

2. Step 2: Choose design that uses interface

   Defining a PaymentMethod interface with pay() method lets each payment type implement its own logic while code depends only on the interface.

3. Final Answer:

   Create a PaymentMethod interface with a pay() method, and implement it in each payment class. -> Option B

4. Quick Check:

   Interface abstraction enables flexible, extendable design [OK]

Hint: Use interface for common behavior, implementations for details [OK]

Common Mistakes:

• Hardcoding payment types with if-else
• Not using interfaces for common behavior
• Using inheritance from concrete classes