I think it's getting to a tipping point where more developers have been burnt by the overly generous promises of MongoDB then those still believing the marketing. I think there would be a lot less hate for MongoDB if it hadn't advertised itself as being more mature than it was. If they'd positioned themselves as a solution for specific use cases and clearly differentiated it's suitability compared to relational databases.
That said, I also think a lot of the blame is due to developers with limited database experience, who believed they could do a 1:1 drop-in replacement of Mysql/Postgresql with MongoDB. Of course that's not possible, but then MongoDB didn't seem to do much to argue against the idea.
Bottom-line, MongoDB isn't optimal for the average CRUD application, and I think there's a growing number of developers who have been burnt trying to use it that way.
If I went into an interview and asked why they chose a document-oriented database, and that one in particular, think I'd be popular? (I like to play with new techologies, too, but it seems odd to see it mentioned as a requirement.)
Many job ads are written by HR, based on a list of technologies that developers naively provided them. Some of our job ads have technologies that we briefly used once in an experiment that was never more than 20% complete, while MongoDB (which we use in production) isn't currently listed.3
Comments
I think it's getting to a tipping point where more developers have been burnt by the overly generous promises of MongoDB then those still believing the marketing. I think there would be a lot less hate for MongoDB if it hadn't advertised itself as being more mature than it was. If they'd positioned themselves as a solution for specific use cases and clearly differentiated it's suitability compared to relational databases.
That said, I also think a lot of the blame is due to developers with limited database experience, who believed they could do a 1:1 drop-in replacement of Mysql/Postgresql with MongoDB. Of course that's not possible, but then MongoDB didn't seem to do much to argue against the idea.
Bottom-line, MongoDB isn't optimal for the average CRUD application, and I think there's a growing number of developers who have been burnt trying to use it that way.
And yet I see a lot of job ads listing MongoDB.
If I went into an interview and asked why they chose a document-oriented database, and that one in particular, think I'd be popular? (I like to play with new techologies, too, but it seems odd to see it mentioned as a requirement.)
Many job ads are written by HR, based on a list of technologies that developers naively provided them. Some of our job ads have technologies that we briefly used once in an experiment that was never more than 20% complete, while MongoDB (which we use in production) isn't currently listed.3