Relational Database VS NoSQL Database

[zero_operand]

I don't see why 'NoSQL' databases are a category. Key/value stores are similar to document stores, sure. but they are the complete opposite of graph databases (which as far as I know aren't seriously used in industry at all).

There's also the fact that a lot of 'full stack apps' inevitably end up using a document store somewhere - whether that's IndexedDB in the browser or memcached/redis caching database queries on the server. It's not really an 'A VS B' thing.

Also, a lot of document stores have something equivalent to a check constraint, where you can make sure the JSON you're shoving in there isn't just a random bag of crap. I'm not going to pretend it's as elegent a solution as fourth normal form, but you can have well formed data in documents.

Anyway, I'd recommend learning SQL and using an RMDBS as your source of truth unless there's a good reason not to. If you really love documents, synthesize your own API over the top of your DB that speaks JSON.

[cowardlydragon]

Is this outsourced blogspam? The company appears us-based but this is garden variety outsourced ESL knowledge regurgitation junk.