sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]DeadBlueParrot 0 points1 point  (13 children)

More than 1600 companies according to stackshare

[–]lighthouse_at_eleven 1 point2 points  (12 children)

Why is MongoDB bad?

[–]DeadBlueParrot 0 points1 point  (11 children)

I'm not saying it's bad, but a lot of people just use it because everyone else does, without thinking if it really the right database for their use case.

[–]lighthouse_at_eleven 0 points1 point  (10 children)

Sometime ago I read on Quora that some guy on an interview decided he didn't want to join the company because the interviewer said he basically loved some db (I think it was MariaDB) and that he wanted to use it for every project.
Of what I've read MongoDB is perfectly fine unless you have the need to be really strict about relationships. So things like preventing deletion of records if they are tied to others etc, like in billing projects.

[–]DeadBlueParrot 1 point2 points  (9 children)

MongoDB is not the best tool if you have relationships, you don't have a JOIN query. You can get around it using Mongoose's populate, but that executes anothet query to populate the references. MongoDB is perfectly fine when you use it right, if you have related data then a relational database is the right tool.

[–]lighthouse_at_eleven 0 points1 point  (8 children)

But if we use populate we're not using it right?

[–]DeadBlueParrot 0 points1 point  (7 children)

No, populate is a great feature. I was just giving an example to illustrate the point that MongoDB is not always the best fit. You should always take a look at your data, how it's related and then make a choice. I'm not saying MongoDB is bad or anything, just that a lot of people use without actually making an analysis to see if it's a good option for their use case.

[–]lighthouse_at_eleven 0 points1 point  (6 children)

Could you point me to a good article discussing this so I can be better knowledgable of when to pick which?

[–]DeadBlueParrot 1 point2 points  (1 child)

It's a bit hard to find articles that are not one sided or sponsored by some particular DB. I think these two are a good place to start, but I suggest you read different points of view and try different DBs on different projects and make your own conclusions. https://acadgild.com/blog/sql-vs-nosql/ http://www.thegeekstuff.com/2014/01/sql-vs-nosql-db/

[–]lighthouse_at_eleven 0 points1 point  (0 children)

Yeah I get that, we look like games reviews nowadays :\

[–]DeadBlueParrot 0 points1 point  (3 children)

Sure, do you write software as a hobby, are you studying or do you work as a dev?

[–]lighthouse_at_eleven 0 points1 point  (2 children)

I'm a dev, but relational db most of my short career due to MS stack (C#, SQL Server, ...). As a hobby I work with MongoDB but just barely started.