I have a system that has several large objects that need to be built and populated each and every time, and these objects may be accessed quite often as well. As a strategy, caching would not be that good for me because there are potentially thousands of these objects which are fairly large. So I propose to serialize the objects to the file system and then deserialize it when I need those objects again. I have several classes that need this serialization functionality.
These objects change as well, so on the next access I check if there were any changes and then I grab only the changes and edit the object, and then reserialize the object.
My question is what is the best way to do this, since I have several classes ... I need some design pattern or strategy that would help me make this a breeze to implement on several classes.
Thanks in advance
View Complete Post