News for hackers. Stuff that matters.
Re:Startup Engineers and Our Mistakes with MongoDB by bdcravens on Wednesday July 19, 2017 @02:32PM (#14806667)
> "It's a poor carpenter that blames his tools"

I think the point of the article is that Mongo is being used mostly by "poor carpenters", and provides worse defaults than SQL does. It's obvious you're operating at an advanced level that young and hungry startups aren't.

Re:Startup Engineers and Our Mistakes with MongoDB by cmenge on Wednesday July 19, 2017 @04:10PM (#14807478)
...which brings us back to the original point: if you use tools you don't understand, chances are things go wrong.
Re:Startup Engineers and Our Mistakes with MongoDB by winter_blue on Friday July 21, 2017 @11:07AM (#14821104)
Key-value stores provide very little. The whole deal with SQL/relational databases, is that they provide much much more. The SQL database like CockroachDB are built on top of RocksDB, a key-value database: https://www.cockroachlabs.com/blog/sql-in-cockroachdb-mappin...

It's the difference between assembly language and a high-level language. Key-value stores are simple, basic, and primitive. What's wrong with that? It's like a farmer saying, I don't want to learn how to use a tractor (it's too complicated), and who chooses to farm with a hand tools instead.

> if you use tools you don't understand

Yea.... key-value stores are incredibly complex and require years of learning to understand.

I could explain a key-value store to a five-year old. In fact, I think even a pigeon can understand the fundamental principle underlying a key-value store. https://en.wikipedia.org/wiki/Pigeon_intelligence

For any non-trivial data model, go with something that can capture your model at a high level, like a relational database or a graph database.