Why are document databases shit?
What would be a valid reason to use one for a project, if any?
>>55755069
>Why are document databases shit?
Many are build around the "eventually consistent" meme, which in other words is shit, as there nearly no use cases for that.
Other than that, there are the technical deficits:
For your example, CouchDB has meh-tier documentation and the tooling is also underwhelming.
>What would be a valid reason to use one for a project, if any?
Literally if you otherwise would load a file from your harddrive.
As you can imagine, there aren't that many valid use cases.
>>55755069
Incompetent young programmers not wanting to learn SQL
>>55755069
NoSQL may be better for:
- Analytics that don't require absolutely consistent numbers.
- Large world games that don't require absolute consistency aka location data for Pokemon Go.
Although ya, MySQL is plenty scaleable for 99% of use cases and could be used for the above cases.
>>55757325
Also the analytics use case is only true if you couple your NoSQL database with a MapReduce (cross-database JOIN system) such as Hadoop