hbase

It goes into a combination of MySQL, HBase and ElasticSearch for processing by various batch and realtime services.

Uncompressed, our test data was at 4GB, but went down to about 400MB after HBase compressed it.

Cassandra, HBase, CouchDB etc even MongoDB have built in scalability as a first order priority from day one and have been largely successful at it e.g.

Not sure they built it, but I remember reading they replaced Cassandra with HBase(?).

The main downside is HBase is operationally complex, but if you've already made the investment there (as we had), it's a great option.

I know all that, I have extensive experience with NoSQL databases like HBase.

Java has expanded into the big data space in recent years and underpins Hadoop, Spark, HBase, Cassandra etc where they are dealing with heap sizes up to 1TB.

We use hadoop, hbase, kafka, scalding, spark and we have a great culture of getting stuff done working with excellent people.

Looking for front-end (React/Flux, Backbone, ES6/CoffeeScript) and back-end (java, hbase, kafka, hadoop) developers who enjoy working in small teams that own significant parts of our products.

Stack Exchange's production setup isn't documented, but we use Cloudera for HBase, relay all data through the tsdbrelay cmd (found in the bosun repo), have HAProxy in front of it all.

So Cassandra has a "logical" key that is the primary key, and the actual key from HBase-like DBs is derrived from cluster key and the primary key.

In addition to Rails work, you'd get hands on experience with Redis, Hbase, PostgreSQL, R and Scala.