Serialization is the process of converting an object into a sequence of bits so that it can be persisted on a storage medium (such as a file, or a memory buffer) or transmitted across a network connection link. This process of serializing an object is also called deflating or marshalling an object.
The serialization mechanism has been added into the Java language for two reasons:
(1) the JavaBeans mechanism uses serialization.
(2) remote method invocation (RMI) allows you to automatically use objects located at another host in the network just like any local objects.
In order to serialize an object, you need the output stream OutputStream, which must be put into the special serialization stream called ObjectOutputStream. After that, you only need to call the method writeObject() to serialize the object and send it to the output stream. . Classes ObjectInputStream and ObjectOutputStream, which respectively implement the ObjectInput and ObjectOutput interfaces, enable entire objects to be read from or written to a stream (possibly a file). To use serialization with files, we initialize ObjectInputStream and ObjectOutputStream objects with stream objects that read from and write to files—objects of classes FileInputStream and FileOutputStream, respectively
Vinayworld class implements serializable interface.

Class vinayworld implements Serializable {
Public String vinay_variable;
Private String vinay_add;

Other class would be

Public class vinayotherClass  {
Public static void main (String args[])
FileOutputStream fos=new FileOutputStream("vinay.txt");
    ObjectOutputStream oos=new ObjectOutputStream(fos);
Vinayworld vw = new vinayworld();

In this code object of the vinayworld class is serialized into a file name vinay.txt
Serialization is a Marker interface -Marker Interface is used by java runtime engine (JVM) to identify the class for special processing.
Use serialization when you need to add data to the serialization stream that is not an object data member.

Externalization is same as Sterilization except that WriteObject() and ReadObject() method are called by JVM during sterilization an desterilization of object. One thing you can do with Externalization is that you can store extra information into object like STATIC variables and transient variables or you can add more information if you have any business need. One good example is compressing and uncompressing of data to send it through network or converting one format to other like a BMP image to JPEG or GIF format.
Externalization allows you to customize how serialization is done. By implementing externalization you are controlling what gets serialized ( and what doesnot ) as versus default serialization where all non-transient attributes get serialized.
For “fat data” classes with a large number of attributes only a few of which needs to persisted, externalization will help you reduce the size of serialized stream and the time taken to serialize the object. But there will be an overhead involved because the runtime has to call your methods to read/write objects.

Performance issue
1. Further more if you are subclassing your externalizable class you will want to invoke your superclass’s implementation. So this causes overhead while you subclass your externalizable class.
2. methods in externalizable interface are public. So any malicious program can invoke which results into lossing the prior serialized state.

Difference between serialization and externalization: When you serialize an Externalizable object, a default constructor will be called automatically; only after that will the readExternal() method be called.Use the Externalizable interface when you need complete control over your bean’s serialization (for example, when writing and reading a specific file format).,339024620,339274531,00.htm


I am an Oracle ACE in Oracle ADF/Webcenter. Sr Java Consultant-working on Java/J2EE/Oracle ADF/Webcenter Portal/ content and Hibernate for several years. I'm an active member of the OTN JDeveloper/Webcenter forum. Passionate about learning new technologies. I am here to share my knowledge. Give your views and suggestion on [email protected] .

More Posts - Website

Follow Me:
TwitterLinkedInGoogle PlusYouTube

  • rahul sharma

    Very nice article.Good for beginners.

  • anurag

    good post.Can you please tell me ,in performance wise which one is better.

  • Pingback:

  • ashwath

    Hey , is there any way to perform the same function as that of externalization without actually implementing the externalization interface ?

  • Dilip kumar

    good answer……… thank u so much…

  • Swati

    I disagree with one point “Externalization is that you can store extra information into object like STATIC variables and transient variables”.
    Its true but even when you override writeObject or readObject method with that you can write transient field as well. So that’s not the difference between impl of serializable and externalizable interface.

  • Rabindra Singh

    I am highly impressed with this blog in serialization. It provides us a good amount of information about this topic. We can also refer following links for more information about this

  • I enjoy what you guys tend to be up too. This type of clever work and exposure! Keep up the awesome works guys I’ve you guys to blogroll.

  • Ramandeep S

    Nice.. From here i understood completely.. Thanks

  • Serialization Vs Externalization | Techartifact I was recommended this web site by my cousin. I’m not sure whether this post is written by him as nobody else know such detailed about my trouble. You are incredible! Thanks! your article about Serialization Vs Externalization | Techartifact Best Regards Rolf Yoder

  • Hello, i read your site, this a best site from me, thanks!

  • I got what you wish, thanks for putting up. Woh I am pleased to undergo this website through google. Thanks For Share Serialization Vs Externalization | Techartifact.

  • thanks for great post.i love this site