News for hackers. Stuff that matters.
Re:The growing irrelevance of MongoDB by Arnt on Wednesday January 14, 2015 @04:59AM (#8885311)
I've used it and been happy. If you want something that's simple to use, know your schema partly but not entirely, and you don't mind losing a few writes, then mongo fits.

Relational databases place such emphasis on reliability. Mongo is generally reliable but only two or three nines, and it's simple.

For example, if you're collecting sub-cent line items for invoices, you might prefer to collect 99.x% of the line items simply over 100% at greater complication and expense, particularly if you can measure x.

Re:The growing irrelevance of MongoDB by gasping on Wednesday January 14, 2015 @06:02AM (#8885533)
What? When would it ever be OK to lose parts of an invoice. Mongo apologists baffle me sometimes. To anyone considering MongoDB, don't be fooled, you probably want to stick with an RDBMS.
Re:The growing irrelevance of MongoDB by Arnt on Wednesday January 14, 2015 @08:13AM (#8885981)
When the parts are cheap compared to the cost of storing them in a real database.

I even know someone who stores invoice items in memcached. Whenever memchached evicts something that hasn't made it onwards to real storage, they lose the ability to invoice the right customer for an ad impression.

Re:The growing irrelevance of MongoDB by mwj on Wednesday January 14, 2015 @07:19AM (#8885753)
What are you talking about? We run a 800+ GB mongo cluster and have never lost data.
Re:The growing irrelevance of MongoDB by mietek on Wednesday January 14, 2015 @06:22AM (#8885582)
This is satire, right? Right?…
Re:The growing irrelevance of MongoDB by Arnt on Wednesday January 14, 2015 @08:03AM (#8885935)
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.

Re:The growing irrelevance of MongoDB by dyadic on Wednesday January 14, 2015 @08:24AM (#8886033)
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.

Re:The growing irrelevance of MongoDB by Arnt on Wednesday January 14, 2015 @08:40AM (#8886107)
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.