3 ms·
From the article: > To start, there are some very practical reasons why we think single server durability is overvalued. Most people should just stop reading
by rdtsc 15y ago
From the article:
> To start, there are some very practical reasons why we think single server durability is overvalued.
Most people should just stop reading at that line.
> If you have durability through a transaction log, then you have to replay it to come back up.
That shows a serious misunderstanding how append-only can work. In CouchDB's case there is no need to replay the whole file just find last consistent piece of data at the end. So seek close to end & find last consistent header.
> If you have a master and slave in the same data center and you lose power, both will have to recover which could take 5-30 minutes.[1]
If you use MongoDB your DB apparently can get corrupted and you won't find out about for another month (link from article):
http://www.korokithakis.net/posts/using-mongodb-for-great-science-part-2/ http://www.korokithakis.net/posts/using-mongodb-for-great-sc...
> If you have a 100 node cluster, worrying about every machine is a liability.
I see having to buy 100 nodes to get durability as a non-starter.
I mentioned this before and I'll say it again that calling their product a database and by default not returning write results is dishonest.
10gen employee (Kristina Chodorow) replying to the article admits that "We did this to make MongoDB look good in stupid benchmarks"
Well that's fine but then just call it rrdtool-ng
- wisty 15y agoI think she was being sarcastic. But yes, it does make MongoDB look good (as in, better than Redis, not just 10X the speed of CouchDB) in stupid benchmarks. MongoDB is designed to be fast by default, which I like. But it can bite you. I like its speed, and its interface, binary data (which saves disk space), and documentation. I'm not sure if it's data structure is sound though. I'd really like something with CouchDB's append only log, and MongoDB's interface (fast and easy), rich updates, and documentation.
- rdtsc 15y agoI don't mind it being fast by default if they don't call it a 'database', they should have made the fast+lose_your_data mode a user configuration not the default. People have lost and will lose their data. They see aha database [check], download [check], run benchmark [check], ok, put in production.