Skip to main content


Encapsulation and information hiding are often used interchangeably. But they are actually different. Information hiding is a design principle, whereas encapsulation is a language facility.
Encapsulation is the process of bundling code and the data it acts on together in one entity. David Parnas describes information hiding as "hiding of critical design decisions", so that the client code does not have to understand the intricacies of the design, and is also oblivious to any changes in design. Encapsulation can happen without information hiding, but will not be effective.
Encapsulation facilitates, but does not guarantee information hiding. Following some simple guidelines will help us create better classes

  • Encapsulation rule 1: Place data and the operations that perform on that data in the same class

  • Encapsulation rule 2: Use responsibility-driven design to determine the grouping of data and operations into classes

  • Information hiding rule 1: Don't expose data items

  • Information hiding rule 2: Don't expose the difference between stored data and derived data

  • Information hiding rule 3: Don't expose a class's internal structure

  • Information hiding rule 4: Don't expose implementation details of a class

  • Read this Javaworld article to better understand these concepts.


    1. Why do we need encapsulation?
    2. Can an OO language exist without encapsulation?

    Note: This post was originally posted on my blog at
    Here are the comments from the old blog post

    AUTHOR: Amol Chaudhari

    Hi Parag,
    The article on javaworld - "Encapsulation is not information Hiding" is very insightful. Thanks a lot for providing us such a good link.
    Prior to reading this article, i never thought of consequences my bad Class design could make. Besides pointing out the subtle differences between encapsulation and information hiding, Paul Rogers has given hints regarding the class organization also, like placing the class variables at the bottom and getters/setters at top makes you focus on the responsibilities of the class rather than the internal data structure. He also hints on the possible choice of method names, like using getPosition() rather using getPositionArray().

    AUTHOR: Parag

    Hi Amol,

    Thanks for the feedback. I am glad you liked the article. Encapsulation is an often misunderstood concept. I especially liked the example of how making an array member private but exposing the fact that the collection is actually an array breaks the concept of information hiding.

    Design decisions do have very real implications. Bad design always accumalates what we call design debt, which has to be paid off at some point of time.

    AUTHOR: Rashmi

    Although we often see the terms 'Encaptulation' and 'Data Hiding' in all OOP articles but often fail to provide a difference between them in terms of a defination.This article was a great help.
    Sir it would be very useful if you could explain the rules for information hiding through a code in java

    AUTHOR: Parag

    Thanks for your suggestion. I will update the post soon with a code example.


    Anonymous said…
    Hi Parag,
    The post is really helpful for understanding one of the core OOP concept.

    I think there should be some visual element to this post which people could remember this distinction always.

    In my blog ,I had tried to do the same in explaination of Abstraction and Encapsulation.

    I would appreciate,If you could comment on my understading about these two concepts.

    Popular posts from this blog

    My HSQLDB schema inspection story

    This is a simple story of my need to inspect the schema of an HSQLDB database for a participar FOREIGN KEY, and the interesting things I had to do to actually inspect it. I am using an HSQLDB 1.8 database in one of my web applications. The application has been developed using the Play framework , which by default uses JPA and Hibernate . A few days back, I wanted to inspect the schema which Hibernate had created for one of my model objects. I started the HSQLDB database on my local machine, and then started the database manager with the following command java -cp ./hsqldb- org.hsqldb.util.DatabaseManagerSwing When I tried the view the schema of my table, it showed me the columns and column types on that table, but it did not show me columns were FOREIGN KEYs. Image 1: Table schema as shown by HSQLDB's database manager I decided to search on StackOverflow and find out how I could view the full schema of the table in question. I got a few hints, and they all pointed to

    Fuctional Programming Principles in Scala - Getting Started

    Sometime back I registered for the Functional Programming Principles in Scala , on Coursera. I have been meaning to learn Scala from a while, but have been putting it on the back burner because of other commitments. But  when I saw this course being offered by Martin Odersky, on Coursera , I just had to enroll in it. This course is a 7 week course. I will blog my learning experience and notes here for the next seven weeks (well actually six, since the course started on Sept 18th). The first step was to install the required tools: JDK - Since this is my work machine, I already have a couple of JDK's installed SBT - SBT is the Scala Build Tool. Even though I have not looked into it in detail, it seems like a replacement for Maven. I am sure we will use it for several things, however upto now I only know about two uses for it - to submit assignments (which must be a feature added by the course team), and to start the Scala console. Installed sbt from here , and added the path

    Inheritance vs. composition depending on how much is same and how much differs

    I am reading the excellent Django book right now. In the 4th chapter on Django templates , there is an example of includes and inheritance in Django templates. Without going into details about Django templates, the include is very similar to composition where we can include the text of another template for evaluation. Inheritance in Django templates works in a way similar to object inheritance. Django templates can specify certain blocks which can be redefined in subtemplates. The subtemplates use the rest of the parent template as is. Now we have all learned that inheritance is used when we have a is-a relationship between classes, and composition is used when we have a contains-a relationship. This is absolutely right, but while reading about Django templates, I just realized another pattern in these relationships. This is really simple and perhaps many of you may have already have had this insight... We use inheritance when we want to allow reuse of the bulk of one object in other