Why I don't use MongoDB

This is the worst video that compares dbs.

I switched to it a few months ago. Then I switched back. There's so much functionality you'd think it'd provide, of which it does not. So it really doesn't solve many problems. But it can actually introduce them. In fact, just about everything, you could do with a SQL JSON type. SQL feels old, but MongoDB feels like it was made in the early 00's and abandoned mid way through development.

All totally wrong

There is only one reason for mongo. It's free to use for learning todo apps. Because of it, there are billions shity courses like React+Mongo+Mongoose+other junk. Only human greed keeps this shit alive.

I don't use mongodb because I don't know about it

Aggregations is how you handle joins. This is something Firebase doesn’t have without manual functions. Graph databases are where it is at. Try redisgraph, neo4j, and if all else fails supabase.

Love the video and the perspective!!!!

How about Supabase? Supabase vs Mongodb. Which would be good for a react native / flutter app?

wouldn't graphql with mongoDB solve a lot of those problems (ie. no schema and being able to query a bunch of data with one query)... im new to any kind of persistent data storage so just wondering!

I am currently working with mongodb Atlas free cluster
It is very slow for getting data and maximum time the database is not connected
Mongodb is giving very hard time

I wonder is this kid knows something called "aggregation" in MongoDB

What's your updated opinion on this

But there are refs in there

Of course you can do joins in MongoDB! $Lookup in the aggregate pipeline. Your statement about consistency is totally BS. You have full ACID transactions even across shards. Do some research before making a bunch of crap statements.

Where are you hosting your PostgreSQL databases?

almost everything you said about mongodb is wrong

Mongodb is garbage

Neo4js

You can query alot of dable (table with data in mind :D). I had to pause and finish laughing. Funny how the brain works.

So Funny that I made a video last week with the exact same title. But my reasons are completely different.

'datle'

Dislikes tells more if you want to know Why not! :D

now a days mysql tries to market it self as nosql + sql

I've given a like to the video only for the opportunity to read some great comments. Thanks, Ben

postgres is both nosql and sql

You can do a manual join where you put a FK in a field and they manually reference it via query

This is plain stupid an one of the most senseless talking i ever heard.

so you did it just get a viral video... isn't it... click bait stuff....... you dump.....

Exactly!!! Mongodb is nothing but pure hype

Mongo is NOT a Database.... It's just that simple... I did not DIG databases in Grad school but ended up taking 3 classes --I use what I learned from that daily and that was back in 1999 when I finished... So learn E-R Database theory, and then sharpen your SQL skills --you'll thank COBB (google him...)

I'm working on one project for my University, and it's about to manage a lot Excel files and use that data to edit, delete, chart, and things like that. and each Excel has 3000 data or more and MongoDB Is a good option in this application, because when they upload the Excel only with one query I can save all this data. And database like MySQL or PostgreSQL, are very slow...

you don't know what NoSQL is and try to use mongodb.This is wrong. You can not be a pilot becouse you drove a car before.

You should consider using GraphDB databases

just talk... nothing preactical

In mongoDB is similar thing like joint called populate

momgo is best db ever no stupid joins tables problems

cool video, I'm interested in your further findings.
and the rumor your were talking about, as far as I know is actually not a rumor, it's possible because of one of the NoSql database's BASE properties: eventual consistency. which means that the transaction finalizes over time. unlike the atomicity of transactions in relational databases. people usually compare ACID vs BASE when comparing SQL and NoSQL databases, take a look if you are interested.

What you thought of DynamoDB ? :) Thank you for the video.

You can build a Schema in Mongo. (And other NoSQL solutions)
Relational and NoSQL have two completely different use cases, and should be used accordingly.
And as you mentioned, NoSQL solutions scale much more betterer than relational.
GridFS can't be done easily in relational afaik. If at all. I mean blobs are cool and all. But document store is pretty rad.

Hi Ben, i have used mongodb in production. Still do actually with a current project. But if I could choose now I would go for pg too. Do you know firebase? I have played with it and it is really nice. For fast online project with offline support and live updating out of the box. I am actually waiting for graphql with neo4j. They are working on it as we speak. That will be the best I think. The schema can be used one on one with the graph database. It is all about relations. We just have to be a little patient for that. Till that time pg. 😃

Mongoose which is a wrapper around MongoDB has relationships which is similar to joins, actually with Mongoose, you just need one reference in your Schema and use a function called populate and it will automatically bring data from multiply Schema together, also it has type checking and enforced structure as-well, also amazing at scaling, just like attaching onto a prototype of a JS object and that's it, also has life hooks as-well.

Mongoose really improves on MongoDB.

I'm afraid you're wrong. Mongoose solves almost all the problems you talked about in this video. Joins is actually possible btw, overall It's really simple and effecient​.

I don't see any reason to use MongoDB over PostgreSQL. You can store json data in PostgreSQL if you want!

One option to address MySQL and Postgres scalability is AWS Aurora. Mongo gets all the attention in the NoSQL world but Cassandra seems to be much faster and more scalable. It would be interesting to see your strategies for testing SQL performance. Great vid!

I mean nosql db's use a ton of ram. And there is no point in using this because you have to upgrade ur server just for the database and have to pay extra for it. What was it 2 years ago 4gb minimum for mongodb

Thanks for this. It was very interesting to hear your views on MongoDB.
I agree that you really need to think about the database design to keep it efficient. Ironically though, I nearly always build a schema with my MongoDB models for validation.
Does the lack of joins issue still apply if one is using GraphQL?
Hopefully a GraphQL/MongoDB/Redis video is still on your list?
I'm also interested in learning a graph database. I was thinking of Neo4j?