Difference between Abstraction and Encapsulation

Brief

It’s almost true that every encapsulation is an abstraction because they both hide something, however, they have their fair share of differences.

Difference between Abstraction and Encapsulation

While both are fundamental concepts related to OOP and they are technically inseparable, they still have their differences in many aspects.

Differences  in “ Definition” of Abstraction and Encapsulation 

– Abstraction is a fundamental OOP concept which emphasizes on all the essential aspects of an object by hiding the irrelevant details to increase efficiency and eliminate complexity. Encapsulation, on the other hand, is a data hiding mechanism which wraps the data and information in a capsule to restrict access from outside world.

Differences  in “Functionality” of Abstraction and Encapsulation

– Abstraction is a data hiding mechanism which highlights only the essential features to make complex programs simpler, while encapsulation, on the other hand, is a method of binding data and codes into a single entity. The idea is to shield the implementation details from external access.
Differences  in “Implementation” of Abstraction and Encapsulation – Abstraction is implemented using abstract class and interface, while encapsulation is implemented using access modifiers. Five types of modifiers are used to encapsulate data: Private, Public, Internal, Protected, and Protected Internal.

Differences  in “Concept” of Abstraction and Encapsulation

– The idea behind abstraction is to focus on what rather than how. Encapsulation hides the internal mechanics of how. For example, when you drive a car, you know exactly what the brake pedal does but you may not know the whole mechanism behind it because the data is encapsulated.
Differences  in “Example” of Abstraction and Encapsulation – Let’s take an example of a smartphone. You know what it does but you may not know how it does what it does. You only care about the display screen and keypad buttons rather than worrying about its inner circuitry. Here, smartphone is an abstract where the inner implementation details are encapsulated.

Abstraction vs. Encapsulation with the comparison table

Abstraction	Encapsulation
- It deals with only the relevant details by hiding the irrelevant ones to reduce complexity thereby increasing efficiency.	- It binds the data and information together into a single entity to protect the data from external sources.
- It refers to the idea of hiding data which is not required for presentation purposes.	- It hides the data and code in order to restrict unwanted access.
- It focuses on what rather than how.	- It hides the internal mechanics of how it does something.
- It hides the unnecessary details on the design level.	- It also hides the details but on the implementation level.
- Information and data is separated from the relevant data.	- Information is hidden inside a capsule for close access.
- It deals with ideas rather than events.	- The idea is to protect the data from outside world.
- It’s implemented using abstract class and interface.	- It’s implemented using protected, private, and package-private access modifiers.

References
 (Thank You All For Your Efforts)
differencebetween.net/technology/difference-between-abstraction-and-encapsulation/