That said, part of the reason Cassandra was attractive to me from the beginning is that unlike master-slave designs like MongoDB (or Bigtable/HBase, for that matter), a p2p design doesn't have the many corner cases around failover and recovery that complicate troubleshooting so badly. This is a primary reason Cassandra has had a very good reliability story since very early on.
What I really meant to say is that it's clear that the engineers behind Cassandra have done their research and chosen an extremely well tested design, while the engineers behind MongoDB seem to be completely winging it, ignorant of the literature and writing (based on my last examination) extremely amateurish code.
> Amazon, Google, Facebook throw mass engineers at problems Cassandra has overlapped with.
> There for, Cassandra is better than "database written by amateurs"
If you have hard evidence post the fucking evidence.
My evidence is "the technology that Cassandra uses"--that is, the SSTable/BigTable storage format and the Amazon Dynamo eventual consistency and distribution model--has been not only peer reviewed and published, but has been serving for years as the foundation of two of the busiest Internet websites in the world. That's real world experience orders of magnitude more extensive and robust than the anything MongoDB can offer.
(In all seriousness, what did they expect? Have they looked at the MongoDB code? Do they seriously believe that the 10gen folks are smarter or better at solving problems than the masses of engineers Google and Amazon have thrown at this problem?)