CockroachDB fares well on the distributed side of the spectrum, and thus shows all the best properties of this kind of systems: replication, resiliency, horizontal scalability, modern ops experience.<p>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?
We currently host our "monolithic" MySQL database on a fairly large VPS on Linode. At least on Linode, to increase storage space you need to double the capacity of the server, thus doubling the cost for each scale up. The idea of simple scaling horizontally is one I've dreamt of for a long time. However it just seems that the problem is not the monolithicness, it's the cost of storage. If we were to use CockroachDB with redundancy the cost would be equivalent to just using Amazon Aurora, which is fully managed!<p>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.
What kind of consistency guarantees can this database provide? Does it support some type of lock so it can be used to give real-time account balances and prevent overdrawing an account?
i am thinking about using cockroachdb to power something like LDAP.<p>but the CIO said no because it has "cockroach" in the name and no one would sign off.<p>should i just do it anyway?