Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Burden of proof is on 10gen, not frustrated customers. This post is believable enough for me to avoid using MongoDB for write-heavy apps.


What if it's not a frustrated customer but a libelous, frustrated competitor instead?


Except that those are not the words on a libelous, frustrated competitor. I've seen these claims validated over and over again both by posts on HN but also people I trust that have worked with MongoDB under load.

Performance benchmarks stop being meaningful when you realize that you can't fix the problem you're having without committing to a system-wide shutdown of unknown duration.

The main point that the author makes is that the creators of MongoDB do not follow rigourous practices. If this doesn't bother you, please go right ahead and use anything you wish.

I hear that /dev/null is really zippy these days.


In most case, I think 10gen will be able to dispute false claims.

With regard to nomongo's post, 10gen can check their record and say whether they did or didn't have a customer with premium support account with similar use case and issues. 10gen can also counter such complaints with testimonials from customers with similar use cases.

But note that nomongo's post is not about individual issues but about his concern that 10gen's priorities are misplaced which he should have wrote first instead of last. Rest was just about how his concern came about. Current status of technical issues he experienced are irrelevant to his concern.


Does it matter?

As a user of MongoDB and Cassandra I am very interested in the sort of discussion that comes out of such postings.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: