java - Serialization: good or bad in a multi-thread environment to maintain a cache? -
which better approach:
- using serialization create cache, or
- simply writing objects in form of string arrays file using delimiters?
recently told serialization creates different thread process, , should not used in multi-threaded environment/application timing constraints need faster processing , less interruption!
so true serialization inefficient in big multi-threaded java project ?
serialization not take place on different thread. while java serializes object, if thread trying modify same object, may run consistency issues state of object being changed while serialization taking place. run in same issue own implementation. answer question "if serialization build cache efficient", suggest @ cache implementations (some open source hazlecast or ehcache).
Comments
Post a Comment