> If you have almost no guarantees to provide, almost any solution would have worked. Within reason. If the failure rate is 1 in 1000 then it's probably not as

> If you have almost no guarantees to provide, almost any solution would have worked. Within reason. If the failure rate is 1 in 1000 then it's probably not as a big a concern as 1 in 10 depending on your use case > In summary, it is not really a useful data point on whether MongoDB is useful or not. As I said in the last sentence - it worked perfectly. In other words the "no guarantees to provide" never actually came up and I don't recall us having any data loss, response time, or write issues.