Goodbye, MongoDB
zopyx.de
Goodbye, MongoDB
1–10 of 123 posts
Re: Goodbye, MongoDB
#2tl;dr We LOVED MongoDB (http://www.zopyx.de/blog/plone-using-highcharts-and-jqgrid) but we got burnt so it's USELESS and BRAINDEAD!
Re: Goodbye, MongoDB
#3A 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.
Re: Goodbye, MongoDB
#4Look, someone else realizing that Codd was right.
Re: Goodbye, MongoDB
#5Wow, how many "Goodbye, MongoDB" stories are coming? The last days had several ones. Not sure if this is already a trend?
Re: Goodbye, MongoDB
#6While some of the author's criticisms are valid, some of them are completely wrong:
> Having no option to perform an operation comparable to UPDATE table SET foo=bar WHERE....
What? db.collection.update does exactly this. See: http://www.mongodb.org/display/DOCS/Updating#Updating-update...
MongoDB fit a nice niche for a read heavy mid-scalability db solution. Every DB has it's niche. Trying to use it outside of what it's good for is going to get you burned. If people just did their research before blindly committing to a platform, we'd see a lot less posts like this.
Re: Goodbye, MongoDB
#7So what is the new solution? Back to relational? Or another type of document store?
Re: Goodbye, MongoDB
#8There is no single way to control the memory usage using system tools except maintaining mongod instances on dedicated virtual machines without running further services. There are numerous complaints from people about this stupid architectural decision from various side and 10gen is doing nothing to change this brain-dead memory model.
Can someone explain to me why this is actually a big issue? Except for really tiny apps, I imagine that having dedicated VMs for your MongoDB actually would be perfectly fine? Probably even preferred?
Re: Goodbye, MongoDB
#9Wow, how many "Goodbye, MongoDB" stories are coming? The last days had several ones. Not sure if this is already a trend?
The trend is this: any loved technology that's been around a little while (Rails, Node, Mongo, etc) makes for dramatic farewells on hackernews. It's not unlike supermarket tabloids.
Re: Goodbye, MongoDB
#10While some of the author's criticisms are valid, some of them are completely wrong: > Having no option to perform an operation comparable to UPDATE table SET foo=bar WHERE.... What? db.collection.update does exactly this. See: http://www.mongodb.org/display/DOCS/Updating#Updating-update... MongoDB fit a nice niche for a read heavy mid-scalability db solution. Every DB has it's niche. Trying to use it outside of what…
I was wondering if he meant copy fields from one column to another, or to modify a value in a document based on the value in another field. I don't think that's possible in Mongo without writing server-side JS or doing it in your client.
Agree with your general point, though - this seems like they have a product/tech mismatch. Though I'd argue that this isn't a niche - read heavy, mid-scalability is a lot of the web.