5 ms·

This is satire, right? Right?…

• Arnt 12y ago
  Not at all. Let me run an example with simple and made-up numbers. Consider two storage solutions used to gather line items to invoices. The line items are ten cents on average. One system is properly ACID, and running it costs one cent per line item on the invoice. The other loses 1% of writes randomly, but its hardware/backup/ops requirements are lower, so it costs just 0.1c/item. The ACID way gives you complete invoices, but you spend 10% of the invoiced amount on the invoices. The lossy way makes your invoices 1% smaller, randomly, but the loss+cost adds up to about 2% instead of 10%. It's like returns on physical goods, really. A random percentage of customers will return goods, you can't control that but you can estimate and monitor it, and optimize if the numbers aren't good enough.
  • dyadic 12y ago
    So, if I want to incorrectly invoice my customers then I should use MongoDB? I don't understand how you can say any of this seriously.
    • Arnt 12y ago
      What's the problem with serving customers and occasionally forgetting some small part of the invoice? Overinvoicing would be bad. But underinvoicing is just another cost of business. If the cost is smaller than the alternative, fine.