"Shortly before JSConf, I had personally spent some time finding out ways to demonstrate that MongoDB will lose writes in the face of failure, to be used in a competitive comparison. Let’s just say that I was successful in doing so, despite recent improvements that 10gen has made. Unfortunately, I am not at liberty to share the results, nor do I think it would be constructive to this discussion. "<p>Why not? Did the author at least contact 10gen with the test case?
I have strong knowledge and some good experience with MongoDB, and now, on my new job, we will use Riak (it's a new project that just starts) as primary server. And while user-friendliness of it is a bit horrifying sometimes (hope I can help to change that) in comparision to MongoDB, Riak's real beauty is it's architecture and main ideas.<p>And yes, these are just different databases. MongoDB is much more RDBMS-like (in terms of consistency, B-Tree indexes and queries), while Riak is what you think of when you think "auto-scalable". So now I love them both :-)
<i>"Have you tried out Riak 1.0? It’s awesome."</i><p>There appears to be a bug in Riak 1.0, rendering it totally useless, at least with the NodeJS Driver:<p><a href="https://github.com/frank06/riak-js/issues/97#issuecomment-2571828" rel="nofollow">https://github.com/frank06/riak-js/issues/97#issuecomment-25...</a><p>tldr; Executing a save then remove then a getAll yields a 500 error.<p>...so we moved our app to MongoDB. Critical mass in the community and the myriad of 3rd party drivers and tools that depend on each other means I'd vouch this kind of issue has better chance of being fixed quickly if it occurred in the NodeJS MongoDB native driver.<p>In our case, we are yet to have any specific needs of a NoSQL DB, just one that works, and this experience gave me no confidence in the Riak ecosystem. Sorry guys.
"Unfortunately, I am not at liberty to share the results, nor do I think it would be constructive to this discussion."<p>- I don't understand this mindset. Forgive me for being naive, but if we're to "toast to the challenges and all become stronger, more proficient, and more successful as a result," then why don't we share these edge cases and fix them?