A good read. I'm working on a relatively large project now, written in Node (whee), and I was considering going full-koolaid with Mongo. I think I may stick to MySQL.
Give PostgreSQL a shot if you're still considering databases.
Goodbye, MongoDB
21–30 of 123 posts
Re: Goodbye, MongoDB
#22I'm amazed at all these (excuse me) idiotic articles. People/projects have different requirements, so there are many databases around(relational and nosql and key/value). Just because your needs do not match MongoDB's (or MySQL's or ...), does not mean the technology is useless.
Re: Goodbye, MongoDB
#23A good read. I'm working on a relatively large project now, written in Node (whee), and I was considering going full-koolaid with Mongo. I think I may stick to MySQL.
It's not ready for primetime in DBs that require a great deal of relational mapping. Best cases are apps with very compartmentalized documents, a more robust caching server or something that doesn't require a lot of cross model mapping.
We found out the hard way with our app, with which we wanted to do a lot of associating and joining of information. You either get locked into the document, or locked into writing interpretive code, and neither case is fun to work around.
Re: Goodbye, MongoDB
#24Wow, how many "Goodbye, MongoDB" stories are coming? The last days had several ones. Not sure if this is already a trend?
IIRC We've had several "Goodbye CouchDB" articles in the past few weeks too. What's the under/over on the inevitable "Goodbye Riak" wave?
Re: Goodbye, MongoDB
#25Actually, using mmap-ed files is a great idea. It's precisely what Varnish does too.
Re: Goodbye, MongoDB
#26Look, someone else realizing that Codd was right.
Right about what, exactly? The relational model certainly has its advantages, but it is not without its disadvantages, either. When it comes to databases, there's no one model that caters for every situation.
Re: Goodbye, MongoDB
#27tl;dr We LOVED MongoDB ( http://www.zopyx.de/blog/plone-using-highcharts-and-jqgrid ) but we got burnt so it's USELESS and BRAINDEAD!
That's the common pattern. MongoDB is easy and convenient when you first start using it, but you hit the limitations pretty quickly. I had the same experience.
Re: Goodbye, MongoDB
#28A good read. I'm working on a relatively large project now, written in Node (whee), and I was considering going full-koolaid with Mongo. I think I may stick to MySQL.
Give PostgreSQL a shot if you're still considering databases.
I love Postgres, but I'm building something for OSS use and most unzip-and-deploy devs don't know how to set up Postgres.
Any additional information that you might be able to give me that might convince me?
Re: Goodbye, MongoDB
#29I keep reading about how mongo's use of memory mapped files is real bad. Isn't that the same technique used by varnish cache and that's what makes it awesome? Can someone explain please?
Re: Goodbye, MongoDB
#30This is kind of a strange list of complaints.
MongoDB memory management is a legitimate concern... but not because it's hard to control memory usage of a single mongod.
"More granular locking" is a temporary, non-scalable solution?
I've run out of energy, actually, but really?