Real-time feed processing with Storm
datasalt.com
datasalt.com
Also, given a set of nodes a set of input data, is end to end latency consistent?
Storm is meant to be distributed across multiple nodes, and even if they are different machines on the same hardware I think whatever communication system storm uses is going to be orders of magnitude slower than any direct memory bus. So if latency is your goal, you probably have to stick to tried and true, whatever that may be (GPU server farms?)
However, I bet it'd be perfect for a market analytic systems, where it can scale to consume and create massive amounts of data in near real time. Maybe as a compliment to your latency sensitive system in some way.
I bet nathan could answer better though.
Storm isn't intended for sub-millisecond type processing, but latencies on the order of milliseconds is certainly doable on Storm. Obviously a lot of that depends on how complex your processing is.
Currently we are using a proprietary CEP platform that has issues with scaling as the number of deployed models (i.e. data consumers) goes up.
Storm's topology based approach maybe worth some investigation because it would allow the addition of more compute nodes transparently as our needs expand. I will take a more detailed look.
I would be interested in learning more about said implementations.
Other hedge funds are also using hardware based solutions. But more likely GPU based solutions for number crunching.
If you are interested I would recommend checking out the forums at wilmott.com or at the Nuclear Phynance [sic] board. Wilmott magazine also has had a few articles on models written in CUDA for pricing options etc.
http://www.hpcwire.com/hpcwire/2007-06-08/high_frequency_tra...
Exegy is one company I'm familiar with, based in St. Louis, MO.
You can also email me if you want to know more.