Comments on: Serialize / De-Serialize Java Object From Database

By: Yousuf Zaman

Yousuf Zaman — Wed, 18 May 2011 08:34:36 +0000

I have a complex object which contain a huge tree, to building this tree it make a huge pressure on database and tree building process happens regularly.
So, in this case is this good practice – if i try to implement the tree like bellow ?
i know when the tree data will change to database, so when the tree database[related tables for tree building] is changed , then i will build the tree object from related tables and put/save the tree object to database using serialization. so that no need to create tree object for all tree building request, only need to retrieve the object from database.

Is this will be a good practice or decision? can u please reply?

By: mohan

mohan — Fri, 29 Apr 2011 10:43:54 +0000

nice example but i want to store some employee type object how can i store?

By: Usman

Usman — Wed, 22 Sep 2010 19:12:54 +0000

Nicely explained.
Thanks

By: Tousif Khan

Tousif Khan — Wed, 28 Jul 2010 04:43:02 +0000

Hi,
A good post like this is always appreciable. Thanks for the post. But people are looking for XML and CSV as the object data stores. For persisting in databases, we have other tools( like ORM’s ) are available. Any way. a nice Post :D.

By: Eliza sahoo

Eliza sahoo — Wed, 27 Jan 2010 06:14:43 +0000

Good one .I was looking for the answer since some days.thanks it helped me a lot.

By: Joe

Joe — Wed, 13 Jan 2010 11:18:01 +0000

Vinit,
In my previous post for serialization, I mentioned that, “don’t use java serialization as a replacement for database”. As, “This is not the primary purpose of java serialization”.

To serialize you can use database as a medium, but I say “don’t use serialization as instead of database”.