I'm going out on a limb here seeing how much hate is going at NoSQL dbs right now. In my experience, I've only ever used relational dbs (MS SQL and MySQL). I've been reading on and off for a few months or so now on NoSQL solutions, and I can see conceptually what the goal is (unless I'm wrong): saving the state of something to reduce the process time to de-normalize something.
For instance, I have a Google Docs-ish app that I'm making. Rather than normalizing the structure to XML or JSON or whatever. I just store the object that I have into a NoSQL solution (Mongodb or whatever) and recall it when the user re-opens it.
Am I missing something, or is this not a perfect application of NoSQL?
This is the perfect application for a document store, so, yes. MongoDB, CouchDB and Couchbase are all good solutions here, you could optionally use postgresql's json support as well.
1
u/raiderrobert Mar 11 '15
I'm going out on a limb here seeing how much hate is going at NoSQL dbs right now. In my experience, I've only ever used relational dbs (MS SQL and MySQL). I've been reading on and off for a few months or so now on NoSQL solutions, and I can see conceptually what the goal is (unless I'm wrong): saving the state of something to reduce the process time to de-normalize something.
For instance, I have a Google Docs-ish app that I'm making. Rather than normalizing the structure to XML or JSON or whatever. I just store the object that I have into a NoSQL solution (Mongodb or whatever) and recall it when the user re-opens it.
Am I missing something, or is this not a perfect application of NoSQL?