I can store the tick data, although I'm not storing it at the moment (I disabled it for the launch and will test the load that enabling it represents).
I use Cassandra with just 1 node for the moment.
It's kind of that, although the client doesn't talk to the exchange directly, it only talks to the backend. The backend consumes events from the different exchanges, transforms it to a common format, stores it and serves it to the client (in brief terms).
For this kind of data, I'd actually use a Time Series Database like ElasticSearch, InfluxDB, or Riak. They're built for data like this. We're using ElasticSearch at work and it's been wonderful.
I use Cassandra with just 1 node for the moment.
It's kind of that, although the client doesn't talk to the exchange directly, it only talks to the backend. The backend consumes events from the different exchanges, transforms it to a common format, stores it and serves it to the client (in brief terms).