SQLite is so hardcore about being totally unbreakable that they have a section in their documentation dedicated to explaining all the horrible things the OS has to do just to get it to fail: <a href="http://www.sqlite.org/lockingv3.html#how_to_corrupt" rel="nofollow">http://www.sqlite.org/lockingv3.html#how_to_corrupt</a><p>Reading about their testing process is also informative: <a href="http://www.sqlite.org/testing.html" rel="nofollow">http://www.sqlite.org/testing.html</a>
1000 writes in 5 seconds for mongo? Running 1.4, I get ~2500/sec on an old P4 desktop that I was using to test on. I've only recently started working with mongo, and I have no experience working with 1.3, the unstable development version that he lost his data using. I'm having a hard time buying into his comparison.
I used SQLite until I found a query that locked it up seemingly forever. It had 2 inner joins. It worked with 1 inner join - NOT 2. The author of SQLite said "Not my problem buddy, it's yours". So I'm switching to PostGRE (which CAN handle those 2 inner joins) or a Microsoft SQL.