21–30 of 30 posts
i am thinking about using cockroachdb to power something like LDAP. but the CIO said no because it has "cockroach" in the name and no one would sign off. should i just do it anyway?
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. 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…
You've to appeal to their spreadsheets. Generally, lower costs. 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. B…
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...
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.
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 w…
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 w…
Which complexity are you referring to, specifically where CRDB has a better approach?
Interested as we are evaluating both.
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 w…
> Cassandra did not live up to the hype for me because of the complexity 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).
Earlier quoted context omitted.
First things first, you'll want a DB that doesn't have cockroach in the name. I'm only slightly kidding.
When picking clever pun names, it's important to choose words that executives won't feel silly saying. Spencer Kimball, CEO of Cockroach Labs, created the GIMP in college.
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. 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…
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. 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…
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 w…
> Cassandra did not live up to the hype for me because of the complexity Which complexity are you referring to, specifically where CRDB has a better approach? Interested as we are evaluating both.
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.