4 ms·
> I never really managed to figure out why people find them so compelling. This might sound jaded but my feeling is that a lot of developers just looked at JSO
by hnarn 6y ago
> I never really managed to figure out why people find them so compelling.
This might sound jaded but my feeling is that a lot of developers just looked at JSON objects that they were already working with and thought to themselves "actually, it would be cool to just store this directly".
Which, in itself, isn't a bad idea but writing a completely new solution from scratch to a problem that's been solved for decades seems a bit like hubris.
AFAIK many relational databases support JSON today, so I'm not sure what the argument would be to choose something like MongoDB today from scratch if you had the choice of anything.
- nailer 6y agoA half table oriented half document oriented solution is just odd. I’ve worked with JSONB in Postgres. There are many reasons to dislike mongo but “your can do that with PostgreSQL “ isn’t one of them. Querying nested values is is nothing like Rethink or Mongo. Keys could be rows or keys. You’re still having to make one to many relationships for something that should just be an array.