What is the difference between Serializable and Externalizable in Java?

by

To add to the other answers, by implementating java.io.Serializable, you get “automatic” serialization capability for objects of your class. No need to implement any other logic, it’ll just work. The Java runtime will use reflection to figure out how to marshal and unmarshal your objects.

In earlier version of Java, reflection was very slow, and so serializaing large object graphs (e.g. in client-server RMI applications) was a bit of a performance problem. To handle this situation, the java.io.Externalizable interface was provided, which is like java.io.Serializable but with custom-written mechanisms to perform the marshalling and unmarshalling functions (you need to implement readExternal and writeExternal methods on your class). This gives you the means to get around the reflection performance bottleneck.

In recent versions of Java (1.3 onwards, certainly) the performance of reflection is vastly better than it used to be, and so this is much less of a problem. I suspect you’d be hard-pressed to get a meaningful benefit from Externalizable with a modern JVM.

Also, the built-in Java serialization mechanism isn’t the only one, you can get third-party replacements, such as JBoss Serialization, which is considerably quicker, and is a drop-in replacement for the default.

A big downside of Externalizable is that you have to maintain this logic yourself – if you add, remove or change a field in your class, you have to change your writeExternal/readExternal methods to account for it.

In summary, Externalizable is a relic of the Java 1.1 days. There’s really no need for it any more.

More Related Contents:

  1. Get NPE reading null object field when deserializing using Jackson [closed]
  2. What is a serialVersionUID and why should I use it?
  3. Java Serializable Object to Byte Array
  4. How do I use a custom Serializer with Jackson?
  5. How can I save the state of my program and then load it?
  6. Java Custom Serialization
  7. What does it mean: The serializable class does not declare a static final serialVersionUID field? [duplicate]
  8. Why java.util.Optional is not Serializable, how to serialize the object with such fields
  9. Serialization – readObject writeObject overrides
  10. Java: object to byte[] and byte[] to object converter (for Tokyo Cabinet)
  11. Jackson ObjectMapper – specify serialization order of object properties
  12. How are constructors called during serialization and deserialization?
  13. Jackson databind enum case insensitive
  14. What is the JSON View class in Jackson and how does it work?
  15. Ignore missing properties during Jackson JSON deserialization in Java
  16. StackOverflowError when serializing an object in Java
  17. When should we implement Serializable interface?
  18. Java to Jackson JSON serialization: Money fields
  19. Possibility to explicit remove Serialization support for a lambda
  20. How do I add a type to GWT’s Serialization Policy whitelist?
  21. Reverse (parse the output) of Arrays.toString(int[]) [duplicate]
  22. How can I deserialize the object, if it was moved to another package or renamed?
  23. Jackson JSON custom serialization for certain fields
  24. Java serialization of multidimensional array
  25. java.io.StreamCorruptedException: invalid stream header: 7371007E
  26. GSON: how to prevent StackOverflowError while keeping circular references?
  27. Why are readObject and writeObject private, and why would I write transient variables explicitly?
  28. Pass Serializable Object to Pending Intent
  29. GSON does not deserialize reference to outer class
  30. Java serialization, ObjectInputStream.readObject(), check if will block

Leave a Comment