3 ms·

I have been waiting for someone to explain the advantages of the different NoSQL solutions - this article is certainly a good start. I'd be curious to hear, fro

by liamk 16y ago

I have been waiting for someone to explain the advantages of the different NoSQL solutions - this article is certainly a good start. I'd be curious to hear, from people who know the technologies well, if Adam's views on which each NoSQL solution can be used for are correct.

steveklabnik 16y ago
I am not an expert with NoSQL, but from my limited research, this all seems pretty correct and in-line with what I've read about each particular software. Not that I'd expect anything less out of Heroku.
Goosey 16y ago
I was thinking the same thing. I would kill for a detailed analysis of the benefits and trade-offs between the widely different database solutions callously thrown into the single moniker of 'NoSQL'. Heaven knows such articles are/were frequent when comparing various SQL database engines.
jchrisa 16y ago
This round up is fairly accurate. One thing worth mentioning is that all of these tools can be bent to be used outside their comfort zone (just like an RDBMS) so you don't have to have a stack of 5 different databases, if you enjoy getting the job done with one.
dasil003 16y ago
EngineYard did a series of 6 that goes a bit more in-depth, their blog nav sucks though so just use this: http://www.google.com/search?q=site:engineyard.com+%22key-value+stores+part%22 http://www.google.com/search?q=site:engineyard.com+%22key-va... Honestly there aren't any really great comparisons because the people with the really in-depth knowledge about one db or another tend not to have the same depth in the others. Plus there's the fanboy quotient adding to the hype, which initially was really turning me off to the whole NoSQL meme. More recently though I've decided that I can't let the ignorant hype distract me from discovering the real value. In general I still think most apps probably need some kind of relational database (and generally I consider a relational DB a nice hedge against changing requirements), but I'm also spending quite a bit of time on optimizing my own app and it's amazing how certain alternative data stores offer primitives to billiantly pick off real world bottlenecks cropping up in a traditional SQL DB. So for me the best way to approach it has been by looking through the prism of real world problems.

by liamk 16y ago

steveklabnik 16y ago

I am not an expert with NoSQL, but from my limited research, this all seems pretty correct and in-line with what I've read about each particular software. Not that I'd expect anything less out of Heroku.

Goosey 16y ago

I was thinking the same thing. I would kill for a detailed analysis of the benefits and trade-offs between the widely different database solutions callously thrown into the single moniker of 'NoSQL'. Heaven knows such articles are/were frequent when comparing various SQL database engines.

jchrisa 16y ago

This round up is fairly accurate. One thing worth mentioning is that all of these tools can be bent to be used outside their comfort zone (just like an RDBMS) so you don't have to have a stack of 5 different databases, if you enjoy getting the job done with one.

dasil003 16y ago

EngineYard did a series of 6 that goes a bit more in-depth, their blog nav sucks though so just use this: http://www.google.com/search?q=site:engineyard.com+%22key-value+stores+part%22 http://www.google.com/search?q=site:engineyard.com+%22key-va... Honestly there aren't any really great comparisons because the people with the really in-depth knowledge about one db or another tend not to have the same depth in the others. Plus there's the fanboy quotient adding to the hype, which initially was really turning me off to the whole NoSQL meme. More recently though I've decided that I can't let the ignorant hype distract me from discovering the real value. In general I still think most apps probably need some kind of relational database (and generally I consider a relational DB a nice hedge against changing requirements), but I'm also spending quite a bit of time on optimizing my own app and it's amazing how certain alternative data stores offer primitives to billiantly pick off real world bottlenecks cropping up in a traditional SQL DB. So for me the best way to approach it has been by looking through the prism of real world problems.