News for hackers. Stuff that matters.
Re:A Depressive Journey With MongoDB by EwanToo on Thursday January 12, 2012 @07:11AM (#3456038)
Given that his disclaimer reads:

DISCLAIMER You are about to read a long story on how I got burnt with MongoDB and depressed with it. I am not blaming MongoDB, anyone using, advocating or developing it. I am blaming myself for this. MongoDB is a good tool. You can use it but just make sure it is what you need and it handles your requirements very well. This is not specific to MongoDB but applies to every tool we use.

I think it's a bit harsh for people to criticise either him or MongoDB too much.

At the end of the day, it was a big rush job, no time was allowed for testing for scaling, and it fell over.

My only real surprise is that it wasn't Apache that fell over first.

Re:A Depressive Journey With MongoDB by davidw on Thursday January 12, 2012 @07:41AM (#3456105)
> My only real surprise is that it wasn't Apache that fell over first.

The Apache web server is a very well-tested, tried and true piece of infrastructure, even if it's not "hip" these days.

Re:A Depressive Journey With MongoDB by EwanToo on Thursday January 12, 2012 @07:48AM (#3456123)
True, but it's defaults are not really "battle ready" and since they didn't tweak MongoDB in advance, I can only guess that Apache was already pre-configured for that load - perhaps they used it for their existing web servers?
Re:A Depressive Journey With MongoDB by spydum on Thursday January 12, 2012 @09:52AM (#3456480)
I would guess Apache httpd is a tool they are familiar with and comfortable managing. Trying to building a high performance MongoDB system in just a couple days was probably a bad first project with the tool. They really should have just stuck to what they know, until familiar with the new shiny.
Re:A Depressive Journey With MongoDB by dasil003 on Thursday January 12, 2012 @07:47AM (#3456121)
True, but it often needs tuning to handle massive loads.
Re:A Depressive Journey With MongoDB by TheSmoke on Thursday January 12, 2012 @07:53AM (#3456136)
apache had not fallen first because netscaler is load balancing between 26 web servers and they are already pre-configured for all these heavy load.
Re:A Depressive Journey With MongoDB by nphase on Thursday January 12, 2012 @10:59AM (#3456750)
26 webservers and only two mongodb instances? Seems stacked.. Why not set up more instances and split the load across them (sharding, splitting collections across replica sets, etc) or similar?

Also - big question for me: were you using a ridiculously old version of mongo? I have yet to run into anyone who is on 2.0 or 1.8 and is still running master/slave (as opposed to replica sets). Sounds like your writes weren't working when you moved to replica sets because your client wasn't properly configured.

Re:A Depressive Journey With MongoDB by obtu on Thursday January 12, 2012 @11:16AM (#3456812)
People may be prompted to react because the title doesn't reflect the content.