Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!feeder.news-service.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Giovanni Azua Newsgroups: comp.lang.java.programmer Subject: Low-latency alternative to Java Object Serialization Date: Sat, 01 Oct 2011 14:46:55 +0200 Lines: 25 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Trace: individual.net K2hWaY8IQcvXNZlbk+DUPwtaI/264KPOTW+BX4vzZM9GhV7RyH Cancel-Lock: sha1:oKebNSnyqvJD6Kvrc3lAqpnTNzA= User-Agent: Microsoft-Entourage/12.31.0.110725 Thread-Topic: Low-latency alternative to Java Object Serialization Thread-Index: AcyAODMOovCddUB2XU21tFtM+1QTpw== Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:8440 Hi again :) I have this lite Client-Server framework based on Blocking IO using classic java.net.* Sockets (must develop it myself for a grad course project). The way I am using to pass data over the Sockets is via Serialization i.e. ObjectOutputStream#writeObject(...) and ObjectInputStream#readObject(...) I was wondering if anyone can recommend a Serialization framework that would outperform the vanilla Java default Serialization? Three years ago I worked for a "high frequency trading" company and they avoided default Java Serialization like "the devil to the cross" this is a Spanish idiom btw ... :) due to its latency. However, I must say that their remoting framework dated back to the Java stone age and my guess is that the default Serialization must have improved over the years; I don't have hard numbers to judge though. I remember JBoss Middleware implementation having some Serialization framework for this very same reason ... have to check that too. Can anyone advice what would be best than Java Serialization without requiring an unreasonably heavy dependency footprint? Many thanks in advance, Best regards, Giovanni