Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MongoDB security notice

mongodb.com

Post reply on HN
Print view View original

191–198 of 198 posts

Re: MongoDB security notice

#191

Post by pleoxy »

cpursley wrote: post #183
pleoxy wrote: post #182

Earlier quoted context omitted.

I 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... Might I suggest you actually use mongo on a project before engaging furthe…

https://www.dbvis.com/thetable/postgresql-jsonpath/ https://github.com/obartunov/sqljsondoc/blob/master/jsonpath...

Definitely a better solution than the brick wall he hit. Complicated beastie. I can see the appeal if you just love, eat, and breath SQL.

But a query language within a query language feels bolted onto something alien to do something pretty basic. Pass. If I'm teaching this to new engineers, pass also.

Re: MongoDB security notice

#192

Post by skatanski »

mdaniel wrote: post #185
skatanski wrote: post #28

Earlier quoted context omitted.

Recent 7.0.0 version has dropped old and introduced quite broken new query planner. Caused a lot of our queries to miss. We’ve had the displeasure to work with the support on multiple related issues.

Maybe they're moving into the Apple category of "don't use .0 releases"

precisely, don't use .0 releases and don't rush to update immediately. Let others do that work.

Re: MongoDB security notice

#193

Post by Thaxll »

cpursley wrote: post #176
Thaxll wrote: post #142

Earlier quoted context omitted.

How do you scale a single master out of the box?

What's nice about Postgres is there's a ton of Postgres compatible products that do scale for the 10% who actually need it. And it's still all just Postgres / SQL.

Again it's not out of the box and your so called "tons" vary in quality and features.

Re: MongoDB security notice

#195

Post by toasted-subs »

dissident_coder wrote: post #159
toasted-subs wrote: post #100

Almost decided to use MongoDB in a project for the first time. Kind of makes me unsure if it’s going to be the right choice.

If you’re trying to solve a problem and think “I’ll use mongodb”, well now you’ve got two problems. Just pick postgres. If you have unstructured data as input, either put in the effort to create some kind of schema for it if you can or just use jsonb if you can’t.

[flagged]

Re: MongoDB security notice

#196

Post by toasted-subs »

clwg wrote: post #174
merek wrote: post #138

Earlier quoted context omitted.

Legitimate question, please don't downvote. Are you basing this opinion on: - popular HN opinion - issues that Mongo experienced in its infancy - mis-modelling highly relational data on a non-relational DB, and blaming the DB for ensuing problems Or are you basing it on extensive experience with wide range of use cases?

I'm of a similar opinion. I experienced all the issues of MongoDB's infancy; it wasn't a good time, but the mmap functionality seemed worth it at the time if you had enough memory or constrained your access patterns appropriately. Nowadays, PostgreSQL has JSON/JSONB types, a full suite of extensions like pgvector and PostGIS, and I can scale with Citus or use it in any of the big managed clouds. From a functionality…

[flagged]

Re: MongoDB security notice

#197

Post by cpursley »

winrid wrote: post #189
cpursley wrote: post #179

Earlier quoted context omitted.

Except you can have objects in Postgres via jsonb; there's no trade off and you're both future and vendor proofed.

Yeah, there is. PG has its own warts that Mongo does not have. Also the JSONB query language sucks. See appending an array in PG [0] vs Mongo [1]. Also PG does not provide a way to atomically append to the array, you have to lock the row via SELECT ... FOR UPDATE. Mongo's $push, $set, etc, are atomic. [0] https://pastebin.com/v2MiV8PE [1] https://pastebin.com/RmLuGzAY

Okay, so use a server side language to do it.

Re: MongoDB security notice

#198

Post by winrid »

cpursley wrote: post #197
winrid wrote: post #189

Earlier quoted context omitted.

Yeah, there is. PG has its own warts that Mongo does not have. Also the JSONB query language sucks. See appending an array in PG [0] vs Mongo [1]. Also PG does not provide a way to atomically append to the array, you have to lock the row via SELECT ... FOR UPDATE. Mongo's $push, $set, etc, are atomic. [0] https://pastebin.com/v2MiV8PE [1] https://pastebin.com/RmLuGzAY

Okay, so use a server side language to do it.

that only solves half the problems I mentioned... :)
Post reply on HN