6 ms·
My biggest hold up to investing time learning how to harness "noSQL" data stores is that there are so many young-ish projects and I'm afraid of picking a loser.
by sant0sk1 17y ago
My biggest hold up to investing time learning how to harness "noSQL" data stores is that there are so many young-ish projects and I'm afraid of picking a loser. Couchdb, mongoDB, Redis, TokyoCabinet, etc, etc.
Seems like it's too early to cast lots, and I'll just stick with what I know for the time being. Is that prudent of me or just naive?
- evgen 17y agoThe tricky thing is that there is not going to be a single winner here. What we are seeing is data moving out of a creaky (albeit very capable given certain conditions) silo and the managing it is becoming more task-specific. Each of the databases you mention has its own strengths and weaknesses depending on what you want to get out of it, the nature of your data and access patterns, and the environment in which it will be deployed. Right now I would suggest that you just watch the space, become conversant in the various models (especially the weaknesses of each) and take each for a small test drive so that you have a basic understanding of what each particular model is capable of.
- mahmud 17y agoThe noSQL school includes both key/value databases and bonafide object stores. None of this stuff is new, BerkeleyDB, circa 1986, is as industrial strength as they come. O2, GemStone, Statice, etc. all go back to the 70s and 80s. Just because something is on github doesn't mean it's ground breaking ;-) The future is full of wonderful things that are yet to reach us from Lisp and Smalltalk research of the past.
- silentbicycle 17y agoThe sticking point with BDB is typically its license - if used commercially, you suddenly need a commercial license from Oracle, and the cost is unspecified.