4 ms·
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
by erikrothoff 9y ago
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!
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.
- dx034 9y agoWould be great to have cloud VPS without RAID for exactly those cases where redundancy is handled a level above. Could probably be offered much cheaper than current VPS.
- bsg75 9y ago> 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.
- cube2222 9y agoCRDB and Cassandra are to totally different databases. 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).
- erikrothoff 9y agoTurns out for Cassandra to work properly you need double the storage space that you max want available, otherwise it can't vacuum properly. So if you want to be able to store 1 TB, you need 2 TB, and if you go over 1 TB, it's not guaranteed to be able to vacuum at all. 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#gistcomment-1888706 https://gist.github.com/shyamsalimkumar/49a61e5bc6f403d20c55...)? Expect a long migration.