Do you know how/why MongoDB "failed" for the facebook application? It's not really clear what that actually means given your comment. Care to share a link to the story or an explanation if there is any?
Also, I'm glad you informed us about Riak deployments, but the last statement is inappropriate: please don't be rude. And spelling please as "pls" makes you seem immature too.
Nice find. However, I don't see where it says anything about MongoDB failing, though it is mentioned as a NoSQL database. Also:
Another customer, Electronic Arts, uses Basho infrastructure for a system that supports 7 million daily users of Warhammer Online on Facebook, saving each player’s status every half-minute, Falco said.
That's an impressive number of daily users, but it's just saving a status every half-minute? I don't see why MongoDB couldn't handle that just fine, assuming enough nodes (auto-sharding is basically working now right?).
I don't know, that's 230k saves a second .. that's no joke no matter what platform you're using. I am not super familiar with sharding in MongoDB (haven't needed to go there yet) but seems like 230k writes/second would stress pretty much anything, and Mongo only added that functionality fairly recently.
Personally I am not at all worried about having to deal with 230k writes/second, though. If one of my apps ever gets that large, I will expect my far-smarter-than-me head of DB ops to deal with it, then send me an email telling me all about how he'd solved the problem, which I will read with great interest from on board my gold-plated yacht.
No so fast with the yacht, he didn't say they're doing 230k saves/sec. That'd be the case if Warhamemr Online saved statuses for 7M concurrent users every 30 seconds. The basho guy said 7M daily users, not 7M concurrent ones.
Also, I'm glad you informed us about Riak deployments, but the last statement is inappropriate: please don't be rude. And spelling please as "pls" makes you seem immature too.