I would also check out Thrift (http://developers.facebook.com/thrift/) and
other solutions which use compile time generation instead. We use our own
such approach for everything internally. The thing I like most about these
approaches is that you don't have to worry about NotSerializableExceptions
at runtime, and it's much easier to maintain compatibility (I would argue
that reliably maintaining compatibility is almost impossible with
serialization without a robust test suite which easily counteracts the
simplicity of serialization).
> Do any of you guys have experience with Java serialization and what
> kind of overheads it causes? As far as I know, it produces very large
> messages and is not particularly fast, so I am concerned about that
> given that it is pervasively used in our system core for sending
> messages between daemons over our messaging API.
> One possible alternative is http://xstream.codehaus.org/ which can be
> tuned to produce fairly small messages (by aliasing class names and
> types for example). However, I have no sense of the speed. I will
> do some performance tests.
> Comments, questions, etc?
> [ Rodrick R. Brown ]
> http://www.rodrickbrown.com > http://www.linkedin.com/in/rodrickbrown >
> This list is hosted by DevelopMentor(R) http://www.develop.com >
> View archives and manage your subscription(s) at
> http://discuss.develop.com >