As one of the many who was burned by the false promise of MongoDB early in my development career, I can safely say that this is a spot-on summary of the problem of MongoDB.
MongoDB is an incredible piece of technology, and in the space where it is needed, it works incredibly well. The problem is that the space it works well in is orders of magnitude smaller than their marketing suggests. Sadly, I think the following tweet they put out a few months ago shows that they are still marketing to the wrong demographic, though developers have known this long enough by now to promptly call them out on it (make sure to click-through to the comments).
MongoDB
@mongodb
A friendly reminder! 😉
16:39 PM - 10 Sep 2018
9012735
SQL has been around for decades and there's a reason why; it's the right choice of technology for most situations, while NoSQL is there to pick up the slack for the specific situations where SQL cannot compete. Fundamentally, it should not be used in places where SQL suffices, because it was not created to be a SQL replacement. NoSQL was created to solve a different class of problems. SQL and NoSQL are not interchangeable, don't fall into the trap of thinking they are.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
As one of the many who was burned by the false promise of MongoDB early in my development career, I can safely say that this is a spot-on summary of the problem of MongoDB.
MongoDB is an incredible piece of technology, and in the space where it is needed, it works incredibly well. The problem is that the space it works well in is orders of magnitude smaller than their marketing suggests. Sadly, I think the following tweet they put out a few months ago shows that they are still marketing to the wrong demographic, though developers have known this long enough by now to promptly call them out on it (make sure to click-through to the comments).
SQL has been around for decades and there's a reason why; it's the right choice of technology for most situations, while NoSQL is there to pick up the slack for the specific situations where SQL cannot compete. Fundamentally, it should not be used in places where SQL suffices, because it was not created to be a SQL replacement. NoSQL was created to solve a different class of problems. SQL and NoSQL are not interchangeable, don't fall into the trap of thinking they are.