I'm with you on this, I have a product that is based on MongoDB and, though customers haven't complained about these issues and it's easy to stick your head in the sand when you haven't had any issues, the response by MongoDB is troublesome.
For instance, compare MongoDB's response to elastic's response:
Initial response to "Call me maybe: Elaticsearch":
That is how you respond to a negative jespen test. It's particularly illuminating since elasticsearch doesn't actually bill itself as primary storage and they take resiliency seriously as opposed to MongoDB who do consider themselves primary storage and they do not.
For instance, compare MongoDB's response to elastic's response:
Initial response to "Call me maybe: Elaticsearch":
https://www.elastic.co/blog/resiliency-elasticsearch/
Their ongoing status on resiliency:
http://www.elastic.co/guide/en/elasticsearch/resiliency/curr...
That is how you respond to a negative jespen test. It's particularly illuminating since elasticsearch doesn't actually bill itself as primary storage and they take resiliency seriously as opposed to MongoDB who do consider themselves primary storage and they do not.