4 ms·
Is there any data store that has come out of these tests looking good? Every Aphyr post I've read had a pretty big failure at some point, even for datastores I
by StavrosK 11y ago
Is there any data store that has come out of these tests looking good? Every Aphyr post I've read had a pretty big failure at some point, even for datastores I considered solid, like Riak or Cassandra.
- iyn 11y agoThat's the questions that I ask myself every time I see "Call me maybe" posts. Is there a good solution?
- tedunangst 11y agoI think the takeaway, about a dozen posts back, was that your clustered database is shit and you shouldn't rely on it. Sharding at the client level may be the best approach. Sometimes the old ways are best.
- mjb 11y agoThose are fundamentally different things. Sharding is a scaling strategy for reads, writes and data size. It doesn't address durability (which many distributed databases do). It doesn't address the discoverability problem of how you know which piece of data is where (easy if you have a well-distributed natural key, potentially difficult if you have a poorly distributed natural key, potentially obscenely difficult if you don't have a natural key). It doesn't address data locality (it can, but then you need to migrate keys, and end up with a second-order 'which key is where?' problem). Most crucially, it doesn't address what you need to do if you have to do transactions (of any kind) across shards. You can try invent something to do that. You may get it right (probably using consensus or 2PC), or you may get it fundamentally wrong. Either way, it's a tricky problem. Sharding is good, for sure. It's not a replacement for this kind of technology. Aphyr is doing great work keeping vendors honest, and making sure they live up to their marketing. I don't think any of this says that clustered databases are inherently shit.
- tedunangst 11y agoThat's fair. I may have been a little cavalier with the use of the word shit. Though I note auto sharding is a headline feature for many systems tested. And as for durability, many seem to fall short of rsync running out of cron.
- acconsta 11y agoZookeeper came out looking good: https://aphyr.com/posts/291-call-me-maybe-zookeeper https://aphyr.com/posts/291-call-me-maybe-zookeeper
- helper 11y agoAlso riak with 'allow-mult' turned on: https://aphyr.com/posts/285-call-me-maybe-riak https://aphyr.com/posts/285-call-me-maybe-riak
- StavrosK 11y agoHuh, compared to what the other datastores got, that's high praise. Too bad zookeeper is more for configuration management rather than for storing generic data.
- spullara 11y agoFoundationDB... which is probably one of the reasons that they were acquired. Aphyr mentions them at the end of the article: "You might adopt a different database–though since Galera is the first distributed SQL system I’ve analyzed, and FoundationDB disapparated, I’m not sure what to recommend yet."
- tveita 11y agoI don't think Aphyr ever tested FoundationDB, that I can find. They ran some tests themselves using the Jepsen framework, but given that a large part of the testing is setting up an environment that exposes the system's weaknesses, that doesn't give me the same level of confidence.
- spullara 11y agoHe worked with them on the Jepsen test that they ran. You can ask him what he thinks about it on Twitter.
- lostcolony 11y ago'Looking good' is pretty subjective. While a lot of these datastores include some sort of "oh, and you can use it this other way", and their marketing documents make it sound like it is totally suitable, the point of these tests is to see what purpose you can put these datastores to and have them be a proper fit. While some are basically "you can't use this unless you really don't care about your data", the two you list are actually great examples of "provided you use them in their niche, they're great; otherwise, they're not". Cassandra, use when writing high volumes of AP immutable data. Riak, use with CRDTs for AP mutable data.
- vogan42 11y agoI don't think riak came out looking too bad, was more documentation than anything. https://aphyr.com/posts/282-call-me-maybe-postgres https://aphyr.com/posts/282-call-me-maybe-postgres Also seemed solid
- deleted 11y ago[deleted]
- threeseed 11y agoPostgreSQL was running only on a single machine i.e not clustered. It is irrelevant in this discussion.
- baudehlo 11y agoTo be fair, most people who think they need a "big data" solution would do just fine with a Postgres single instance install.
- threeseed 11y agoThere is far more aspects to big data than just how much data you store. But regardless you completely missed the point. PostgreSQL was tested as a single instance. Everything else clustered. It's apples and oranges. The clustering part is the hard part here.
- baudehlo 11y agoI didn't miss the point - I totally get it. My point was simply to remind people that over complicating your situation and going for a "big data" store is usually a mistake when there's something that will keep your data safe when it isn't as big as you assume it's going to be.
- ddlatham 11y agoHBase. With the caveats that it's piggy backing off the success of Zookeeper, and the tests were not run by Kyle himself: http://old.eng.yammer.com/call-me-maybe-hbase/ http://old.eng.yammer.com/call-me-maybe-hbase/ http://old.eng.yammer.com/call-me-maybe-hbase-addendum/ http://old.eng.yammer.com/call-me-maybe-hbase-addendum/
- curiousDog 11y agoI think SQL Azure that uses SQL Server underneath would pass his tests. But then again it's not hot valley stuff put out by engineers who discovered distributed systems 2 years ago.
- cpitman 11y agoIsn't the bigger problem that it is impossible to test any DBaaS effectively since we cannot purposely cause failures and network partitions? The general theme of Call Me Maybe has been that these projects overstate their actual capabilities, and the only way to know is to check.
- curiousDog 11y agoYeah, my bad, you're right. Perhaps someone from Microsoft should get in touch with him to run the tests.