This is no small feat, and - personally - I am sold on it. Yet, looking at its benchmarks (pre 2.0), and knowing how carelessly some enterprise software is written, how would I convince a pointy haired boss to leave the practically monolithic mega-pumped Oracle RAC server he is accustomed to, and go down the distributed route?
If Oracle is well-established, it's going to be tough. It isn't just the cost of Oracle and doing business with them, it's the cost of all the work associated with making the transition. Code-rewrites, retraining ops, and so on.
If there's an opportunity for a greenfield, small project that would benefit from having a distributed backend then try that. Be prepared to show that it's not just low-cost, but it is easier to implement.
If you are open to trying other options, TiDB (https://github.com/pingcap/tidb) is also a good choice. A use case is just published on Datanami today: https://www.datanami.com/2018/02/22/hybrid-database-capturin...
I'm only slightly kidding.
Spencer Kimball, CEO of Cockroach Labs, created the GIMP in college.
That being said I'm very excited about CockroachDB. Cassandra did not live up to the hype for me because of the complexity and now that DataStax has split up with Apache in a weird way, it feels like a less appealing option.
Which complexity are you referring to, specifically where CRDB has a better approach?
Interested as we are evaluating both.
CockroachDB is full SQL ACID database. With transactions, consistent indexes, joins. It's also strongly consistent overall.
Cassandra is really just a key-value store, with a hierarchy of sorting keys as part of the key, so that you can do range scans with good performance (and various access patterns). Indexes are asynchronously updated (as far as I know). No transactions nor joins. Its consistency is varying (configurable).
Also, Apache Cassandra and DataStax Cassandra did a hard split recently, so the docs are no longer in sync, making it a lot harder to search for stuff if you're using Apache Cassandra.
Also, patch versions of Cassandra are not guaranteed to be binary compatible (sstables), [so upgrading from 3.0.5 to 3.0.9](https://gist.github.com/shyamsalimkumar/49a61e5bc6f403d20c55...)? Expect a long migration.
You can check their customers page: https://www.cockroachlabs.com/customers/
but the CIO said no because it has "cockroach" in the name and no one would sign off.
should i just do it anyway?