7 ms·
Nothing wrong with picking mongo if it's a good fit for your use case.
by pleoxy 3y ago
Nothing wrong with picking mongo if it's a good fit for your use case.
- webappguy 3y agoExactly
- cpursley 3y agoAnd what's a good use case over Postgres jsonb?
- Thaxll 3y agoPostgress is single master which is a huge limitation.
- pleoxy 3y agoWhen one doesn't want SQL for one. Nosql is a fun target to beat up on of late. But there are good, even infamous, reasons to avoid SQL. Particular if you want to accomplish flexible record queries from untrusted clients.
- cpursley 3y agoI’ll ask again, what’s a good use case over Postgres jsonb.
- pleoxy 3y agoAll you do is poop all over the story about postgres. I'm convinced that no use cases will convince you of anything. I'm not really looking to involve myself in a database holy war.
- cpursley 3y agoIs jsonb in Postgres not flexible enough? I dump external json in there all the time (like large API responses). The jsonb operators work well. And there's an escape hatch that lets you easily convert json to a table. And importantly, you get indexes with Postgres.
- pleoxy 3y agoI apologize for being short with you in my previous response. I need to be better about assuming good faith. Your response seems to betray a certain ignorance of mongo. Don't you realize that mongo has indexes? For handling documents, this blog post covers the topic in some depth. https://jimb-cc.medium.com/postgres-jsonb-meets-mongodb-part-1-the-basics-43d9fc95c40b https://jimb-cc.medium.com/postgres-jsonb-meets-mongodb-part... Might I suggest you actually use mongo on a project before engaging further on the topic. It clearly has had a lot more thought put into it in the context of json documents. If postgres works great for your use cases, great, go be happy with the tool.
- 3y ago