News for hackers. Stuff that matters.
Re:Broken by Design: MongoDB Fault Tolerance by guard-of-terra on Tuesday December 17, 2013 @05:23PM (#6924411)
Please provide a better drop-in alternative or shut up seriously.

SQL is single master and is pain in the ass for many applications. Cassandra didn't happen to work for us. CouchWhatever failed to ever get off ground. Redis - can't say anything about it. That leaves us with what?

Yes, mongodb fails but only after it delivers. Other nosql databases don't get into the delivery phase.

What's there to choose?

Re:Broken by Design: MongoDB Fault Tolerance by SideburnsOfDoom on Tuesday December 17, 2013 @05:31PM (#6924456)
> Please provide a better drop-in alternative or shut up seriously.

He mentioned several. He talked about why he prefers them.

Re:Broken by Design: MongoDB Fault Tolerance by guard-of-terra on Tuesday December 17, 2013 @05:54PM (#6924566)
Maybe he should have written a first article on how they are fantastic for his real-life tasks instead of 100th article on how mongodb is bad despite being really used.

All tree of his recommendations strike me as key-value storage. Key-value storage is both easy to write and not very useful in production. I don't know how much meat they provide over mere key value, but allow me to be wary.

Re:Broken by Design: MongoDB Fault Tolerance by notacoward on Tuesday December 17, 2013 @09:02PM (#6925420)
None of the three are just key/value. Cassandra is a BigTable-like wide column store, and Riak is a document store with some graph capabilities. HyperDex seems closest to Redis with lists/maps/sets, except that it's distributed and fully consistent (i.e. what Redis could dream of being some day). None of those are easy to write, and many people already find them quite useful in production. Stop being flat-out wrong about everything, and do some research.
Re:Broken by Design: MongoDB Fault Tolerance by gaius on Tuesday December 17, 2013 @05:29PM (#6924443)
SQL is a language, not a database...
Re:Broken by Design: MongoDB Fault Tolerance by guard-of-terra on Tuesday December 17, 2013 @05:48PM (#6924538)
All SQL databases share several traits.
Re:Broken by Design: MongoDB Fault Tolerance by gaius on Tuesday December 17, 2013 @05:57PM (#6924593)
Being single-master isn't one of them.
Re:Broken by Design: MongoDB Fault Tolerance by guard-of-terra on Tuesday December 17, 2013 @06:08PM (#6924639)
Being single master without paying extraordinary sums, staffing wizards or both - is.

That is baked into SQL.

I only care about pragmatics.

Re:Broken by Design: MongoDB Fault Tolerance by gaius on Tuesday December 17, 2013 @06:38PM (#6924787)
Re:Broken by Design: MongoDB Fault Tolerance by guard-of-terra on Tuesday December 17, 2013 @06:49PM (#6924844)
Mongodb is 'free' too. Does not mean it will work for you in production. Mongodb does for us. Do we have a half year to figure whether mysql would? No we don't, and it probably won't meet our expectations anyway.
Re:Broken by Design: MongoDB Fault Tolerance by notacoward on Tuesday December 17, 2013 @08:56PM (#6925407)
The author and I are hardly best of friends, but he does deserve credit as co-creator of http://hyperdex.org/ which seems to be a completely credible entry in the NoSQL space. Demanding an exact drop-in replacement is unreasonable. He has come close enough, and contributed to the state of the art in the same field. You're being an ass.
Re:Broken by Design: MongoDB Fault Tolerance by guard-of-terra on Wednesday December 18, 2013 @01:56AM (#6926254)
As an author of Hyperdex it seems unethical for him to go bash competition.
Re:Broken by Design: MongoDB Fault Tolerance by notacoward on Wednesday December 18, 2013 @08:56AM (#6927466)
Well, that's a tricky one. In some ways he has a duty to explain what makes his own project useful and different. That often involves making comparisons to others. All of us in the same or related fields (including me) also have a duty to educate users about tradeoffs and especially about those that can endanger their data, and that often involves using "less stellar" systems as examples.

Unfortunately, there are many who take the comparisons or examples too far, either by making claims that aren't quite true or by "piling on" about things that are already well known. The punishment should be proportional to the crime, and I think there are some who would impose the death penalty for jaywalking. At least half of the sniping from the Riak camp about Cassandra's consistency falls into this category. While some criticism of Mongo is well deserved, at least as much is overkill and far more is just crowd-following by people who don't even understand the issues.

The OP is one of these extremists ("data radical" is his own term). In fact, the reason he and I aren't such good friends is that we disagreed quite sharply about some of the FUD he was slinging to promote his own project.

http://pl.atyp.us/wordpress/index.php/2013/03/is-eventual-co...

I don't think it's unethical for people to criticize related work. In fact, such criticism can be very useful. Many of my own contributions to GlusterFS have been inspired by these discussions, sometimes even about other projects. The key is to keep criticism factual and relevant to some point other that "that project sucks", to avoid piling on, and to offer occasional praise as well as condemnation.

Also, you originally condemned him for criticizing without having contributed an alternative. Now you're condemning him for criticizing when he has. What are the ethics of setting up such a "damned if you do and damned if you don't" situation?