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

181–190 of 198 posts

Re: MongoDB security notice

#181

Post by tgv »

cpursley wrote: post #124
tgv wrote: post #53

Earlier quoted context omitted.

I use it on-prem (well, on a VPS). It stores JSON documents, and it's easy to work with. If your data looks like a tree, it works pretty well, also for large documents. If you depend on relations between documents, you're better off with an SQL database, but note that for many cases --I'd say practically all mundane cases-- there's really no need for relations the SQL way. MongoDB also does relations, but a bit more…

Postgres does all that plus 100x.

I've also tried SQLite, but they didn't do large documents that well. And the project was started before I was aware Postgresql had json support.

But what's the advantage of Postgresql in this case?

Re: MongoDB security notice

#182

Post by pleoxy »

cpursley wrote: post #177
pleoxy wrote: post #157

Earlier quoted context omitted.

All 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.

Is 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.

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 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.

Re: MongoDB security notice

#183

Post by cpursley »

pleoxy wrote: post #182
cpursley wrote: post #177

Earlier quoted context omitted.

Is 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.

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...

Re: MongoDB security notice

#184

Post by mdaniel »

calyhre wrote: post #25
iaresee wrote: post #17

We are completely locked out of our Atlas account and the support portal right now. We Okta-auth with Mongo and all attempts to auth right now are failing with "The request contained invalid data." displayed on their login screen. Of course, the support portal requires you to auth to use it...to get help with auth failing. Anyone else seeing issues getting in to their dashboard? Edit: Auth started working for us and…

Same here with Google SSO

Seeing that reminded me of this recent onoz, which one should fold into their threat model: https://trufflesecurity.com/blog/google-oauth-is-broken-sort... https://news.ycombinator.com/item?id=38670644>

Re: MongoDB security notice

#185

Post by mdaniel »

skatanski wrote: post #28
superduperer wrote: post #18

Are they doing well? Seems like the hype has kind of died down.

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"

Re: MongoDB security notice

#187

Post by booi »

bobnamob wrote: post #171
didip wrote: post #163

Earlier quoted context omitted.

Friends don’t let friends run on us-east-1. Consolidate on us-west-1 or us-west-2 instead.

us-west-1 wouldn’t be my first choice either for

us-west-1 seems small. They routinely run out of the instance size we request and the spot market seems.. unruly

Re: MongoDB security notice

#188

Post by booi »

pleoxy wrote: post #128
iLoveOncall wrote: post #58

Earlier quoted context omitted.

This is too reductive, you can essentially have flexible schemas with most modern relational databases and without the downsides of document-based DBs. In 99% of the cases, even if you need a flexible schema, PostgreSQL will remain the best choice.

Unless it's not.

it probably is though

Re: MongoDB security notice

#189

Post by winrid »

cpursley wrote: post #179
winrid wrote: post #156

Earlier quoted context omitted.

Sometimes this is the case but not always... It's nice to just work with objects in some languages... for some projects. That's engineering - picking trade offs :)

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

Re: MongoDB security notice

#190

Post by winrid »

winrid wrote: post #167
yawaramin wrote: post #166

Earlier quoted context omitted.

But you don't need to horizontally scale if you use a beefy Postgres instance. Horizontal scaling is a problem created by using an inefficient DB in the first place.

I have DB clusters with masters with a terrabyte of ram. Going beyond that is a PITA with warming up cache, backups, and so on. There is a reason there's a huge industry for shared databases. Also, query for query, Mongo isn't going to be that much slower than PG, and faster for some usage patterns...

*sharded
Post reply on HN