Live data from Hacker News

Was MongoDB Ever the Right Choice?

simplethread.com

11–20 of 224 posts

Re: Was MongoDB Ever the Right Choice?

#11

I'm still in charge of a production system serving around 2,000 small to medium websites from a 2-machine MongoDB cluster. It's been running on MongoDB since around 2010 and we have NEVER had any issues. I accept that the unacknowledged writes was a bad decision, but IMHO if you deploy a new database without reading the documentation, you have bigger issues. The reality is that there are some places where speed of mo…

Which is exactly what the author writes. "Was it ever the right sollution? It depends."

Re: Was MongoDB Ever the Right Choice?

#12

I'm still in charge of a production system serving around 2,000 small to medium websites from a 2-machine MongoDB cluster. It's been running on MongoDB since around 2010 and we have NEVER had any issues. I accept that the unacknowledged writes was a bad decision, but IMHO if you deploy a new database without reading the documentation, you have bigger issues. The reality is that there are some places where speed of mo…

Which is exactly what the author writes. "Was it ever the right sollution? It depends."

Seems logically invalid.

If you gave to answer "it depends" on a "was ist ever", you should have written "yes" instead, imo.

Re: Was MongoDB Ever the Right Choice?

#14
post #12

Earlier quoted context omitted.

Which is exactly what the author writes. "Was it ever the right sollution? It depends."

Seems logically invalid. If you gave to answer "it depends" on a "was ist ever", you should have written "yes" instead, imo.

Actually the author writes: "So was MongoDB ever the right choice? Yes, of course it was; like most things in engineering, it depends."

Re: Was MongoDB Ever the Right Choice?

#15

I actually think NoSQL might be better for MVP and prototyping. Why? Because they can handle churn more quickly, and you don't have to worry about scale. Once the data layer starts to resonate around a solution ... then pick the right horse for it.

Why not just use a SQL db that handles json and stick everything in a couple columns? Changing databases is a lot of work, and as far as I can tell, mongo isn’t really providing much value over SQL dbs that already support schemaless json columns.

Re: Was MongoDB Ever the Right Choice?

#17
Since everyone is sharing their opinion and experience with mongodb I think I’ll share mine.

As an appeal to authority I would like to mention that I have relevant vocational qualifications on the subject (more geared towards scalability and operations). Although I don’t believe it really matters - it will to those who assume I don’t understand best practice.

MongoDB itself is not /really/ a valid choice in many scenarios that it was painted as solving. Their only fault is overzealous marketing, it has (in my opinion) very clear pain points that should be avoided, but those painpoints are antithical to why many people used it in the first place.

Most people pick up mongo because it’s painted as being “beginner developer friendly”, I don’t mean new developers, I mean picking it up and running with it, without understanding it, was made to be incredibly easy. But MongoDB itself needs you to understand your data patterns before you start adding shards, so the technology itself depends on you actually sitting down and designing an architecture while understanding that. These goals are at odds with each other.

In MongoDB (as it was when I was using it in full prod 6+ years ago) you -needed- to understand how your data is going to grow and how it will be queried long before you ever created an index. You could not grow after creation. But using it as a plain document store with no searching and heavy sharding on the document ID is the best way to go. And in that scenario it is much better than most competitors.

In nearly every /other/ scenario its a less favourable choice than another technology of some variety.

I would argue the data loss point but I think if that’s not a solved issue it will be, and I’m fairly certain you can configure it to be slower but correct (my memory is bad).

I am not a MongoDB advocate, nor do I hate the technology outright. I strongly dislike how it was marketed as being a panacea.

And for the same reason I avoid PHP, I will attempt to avoid MongoDB.

(As in; it can be done well but the majority of cases will be poorly implemented)

Re: Was MongoDB Ever the Right Choice?

#19

I always supposed that document databases were based on object databases from the early 90s... And that the "NoSQL" craze was simply a continuation of that progression. I mean there is a difference between NoSQL and no schema. The early object databases had schemas. The reason they wanted to abandon SQL was because they believed that they never wanted relational data: they just wanted a persitance layer for their bus…

Mongo's debut was well timed to ride the JSON crazewave.

Re: Was MongoDB Ever the Right Choice?

#20
post #17

Since everyone is sharing their opinion and experience with mongodb I think I’ll share mine. As an appeal to authority I would like to mention that I have relevant vocational qualifications on the subject (more geared towards scalability and operations). Although I don’t believe it really matters - it will to those who assume I don’t understand best practice. MongoDB itself is not /really/ a valid choice in many scen…

MongoDb's overzealous marketing is like my sending out resumes extolling my skills with C/C++ embedded programming.

I guess it's actually lying now that I think of it. People might be justified in being a little bit peeved.

Post reply on HN