Why are people still choosing Mongo over Postgres these days? If there's something I'm missing, I'm genuinely curious as I'm not against json data and frequency use jsonb tables in Postgres.
MongoDB security notice
121–130 of 198 posts
Re: MongoDB security notice
#122Almost 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.
Mongo is never the right choice. Postgres is nearly always the right choice, however.
Re: MongoDB security notice
#123Why are people still choosing Mongo over Postgres these days? If there's something I'm missing, I'm genuinely curious as I'm not against json data and frequency use jsonb tables in Postgres.
[deleted]
Re: MongoDB security notice
#124I never used/tried MongoDB, what are the reasons people choose MongoDB over other DBs?
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.
Re: MongoDB security notice
#125Re: MongoDB security notice
#126This highlights risks of extreme consolidation - even if Atlas customers were not affected it is natural for them to be concerned after announcement overwhelming web site or support channels. More independent MongoDB DBaaS providers is what would offer true redundancy in this case, though it is highly restricted due to SSPL license change. Hopefully FerretDB will be successful building feasible alternative
“Extreme consolidation” - wait till us-East-1 goes down
Re: MongoDB security notice
#127Almost 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.
The problem here is with the hosted service, not the database itself or its performance.
Re: MongoDB security notice
#128Earlier quoted context omitted.
Mongo is the main nosql choice. Mongo is great if you think a flexible schema is good. Mongo is not great if you think a flexible schema is bad. That sums it up
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.
Re: MongoDB security notice
#129Re: MongoDB security notice
#130Earlier quoted context omitted.
Nothing wrong with picking mongo if it's a good fit for your use case.
And what's a good use case over Postgres jsonb?
When 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.