right. read the doc beforehand, and for financial data use the time proven relational dbs. they're "slow" for a reason. for massive user generated content wher

right. read the doc beforehand, and for financial data use the time proven relational dbs. they're "slow" for a reason. for massive user generated content where big numbers of statistics come into play, and noone would die if you lose their hard-composed 140 char tweet, use transaction- and lock-free, easily-sharded, rarely flushed to disk stores.