Abstraction in Java

When I started learning Java, abstraction felt confusing at first. But once I connected it with real-life examples, it started to make sense.

In this blog, I’ll explain abstraction in the simplest way possible—just like how I understood it.

What is Abstraction?

Abstraction means hiding the internal implementation details and showing only the essential functionality.

In my own words:

I focus on what something does, not how it does it.

This idea is actually everywhere in real life.

Real-Life Example (How I Understood It)

Think about a car:

• I use the steering, brake, and accelerator
• But I don’t know how the engine works internally

Still, I can drive the car perfectly.

That’s abstraction.

Why Abstraction is Important

When I started building projects, I realized abstraction helps me:

• Reduce complexity
• Write cleaner code
• Hide sensitive logic
• Make code reusable
• Easily maintain large applications

How Abstraction is Achieved in Java

In Java, I mainly use two ways:

• Abstract Classes
• Interfaces

1. Abstract Class in Java

An abstract class is a class that I cannot create objects from directly. It can have both:

• Abstract methods (no body)
• Normal methods (with body)

Example

abstract class Vehicle {
    abstract void start();

    void stop() {
        System.out.println("Vehicle stopped");
    }
}

class Car extends Vehicle {
    void start() {
        System.out.println("Car starts with key");
    }
}

public class Main {
    public static void main(String[] args) {
        Vehicle v = new Car();
        v.start();
        v.stop();
    }
}

My Understanding

• I define a general idea in Vehicle
• Then provide actual behavior in Car
• I can’t create Vehicle directly

2. Interface in Java

An interface is like a blueprint. It only defines methods, and I must implement them in another class.

Example

interface Payment {
    void pay();
}

class UPI implements Payment {
    public void pay() {
        System.out.println("Payment via UPI");
    }
}

class Card implements Payment {
    public void pay() {
        System.out.println("Payment via Card");
    }
}

public class Main {
    public static void main(String[] args) {
        Payment p1 = new UPI();
        p1.pay();

        Payment p2 = new Card();
        p2.pay();
    }
}

My Understanding

• Same method pay()
• Different implementations (UPI, Card)
• Very flexible and reusable

Abstract Class vs Interface (Simple View)

Feature	Abstract Class	Interface
Methods	Can have both abstract and normal methods	Mostly contains abstract methods
Implementation	Can provide method implementation	Only method declaration (implementation in class)
Inheritance	A class can extend only one abstract class	A class can implement multiple interfaces
Usage	Used when classes share common behavior	Used for defining a common contract
Object Creation	Cannot create object directly	Cannot create object directly

Real Use Cases (Where I See This in Projects)

• Payment systems → Same method, different payment types
• Banking apps → Deposit/withdraw without knowing backend logic
• APIs → Only necessary data is exposed
• Frontend apps → Button click hides backend operations

Abstraction vs Encapsulation

I used to mix these up a lot:

• Abstraction → Hides implementation
• Encapsulation → Hides data

👉 Abstraction = Design
👉 Encapsulation = Security

Conclusion

Once I understood abstraction, I stopped worrying about internal complexity and started focusing on clean design.

If you’re a beginner, just remember:

Show only what is needed, hide everything else.