Hacker News Reader

Comment by PaulHoule | Hacker News Reader

If you like the document db idea there are a lot of choices, especially

which I think gets little attention because people who use it see it as a secret weapon. Too bad about the license though. Also

https://couchdb.apache.org/

and

https://developer.marklogic.com/

View on HN

Also, Postgres. It has built in support for json data types, can index on json fields, and do most of the stuff you'd want to do in mongo while not locking you into that paradigm for the parts of your app that don't need it.

Arango isn't comparable, the Free edition is extremely limited. PostreSQL doesn't say how much you are allowed to store or what you can use it for.

With regard to ArangoDB, the Community Edition is for personal or internal business projects (non-prod, up to 100GB). There is also a managed version and self-manage Enterprise version that companies use with their apps.

Comparison - https://arangodb.com/subscriptions/

Isn't PostgreSQL supporting JSON and queries over them? [1]

[1] https://www.reddit.com/r/django/comments/14f68rz/postgresql_...

It does. See https://www.postgresql.org/docs/current/datatype-json.html

I think it is ugly as hell to work w/ json documents in pgsql but most of the eng managers I’ve known think you couldn’t get fired for choosing pgsql.

It's ugly but having a field that's just a dictionary is really handy and not too ugly.

We use a lot of them for things like "tags" (which can take freeform user- or ml- supplied image tags in key:value format). I adore it. (We tried mongo with one of our annotation systems and regretted it.) It's a very nice way to balance quick development (you don't need a schema change to try a feature for a while) with the benefits of a mostly schema-defined db.

Reply on news.ycombinator.com