3 ms·

I really would like to see Couchbase analyzed... and for aphyr to marry me.

by MCRed 11y ago

mbesto 11y ago
I'm actually genuinely interested in that as well (Not the marrying part), especially considering aphyr and Damien Katz went at it about a year ago: https://twitter.com/damienkatz/status/527588456747499520 https://twitter.com/damienkatz/status/527588456747499520
- willchen 11y ago
  Educational back-and-forth, although unnecessarily biting. TL;DR - Aphyr thinks Damien Katz never read this: https://en.wikipedia.org/wiki/Consensus_%28computer_science%29#Problem_description https://en.wikipedia.org/wiki/Consensus_%28computer_science%...
- augustl 11y ago
  What I find really interesting is that while it appears to me that Katz has very sparse knowledge of databases, he has still managed to create one or two of them, and successfully run a company that sells one. I don't like the thought I had next, but: perhaps knowing about consensus algos and papers actually doesn't matter?
  - Saavedro 11y ago
    well, matter for what? For building software that seems to work, sure, no. But for being able to speak to its capabilities -- or even know what they are, especially in the case of distributed systems it's definitely important. this is why so many of the new DB offerings have docs that are either misleading or wrong -- often the doc writers or even the devs themselves don't know what invariants their system can guarantee and assume several that it can't.
  - DomreiRoam 11y ago
    Depends on the problem you want to solve. CouchDB is a very good document database when you have more read than write and when writer are mostly writing on different documents. If I understand correctly replication conflict resolution is up to the application. So knowing about consensus algo is unnecessary for CouchDB because he doesn't support it. I think it's smart to know a little about the literature; enough to know what battle you don't want to fight. It is not smart to try to develop an engine on the basis that it will need to beat the law of thermodynamic to be possible. But also, “They did not know it was impossible so they did it”, Mark Twain
    - krugster 11y ago
      FWIW, Couchbase != CouchDB: http://www.couchbase.com/couchbase-vs-couchdb http://www.couchbase.com/couchbase-vs-couchdb +1 For Jepson on Couchbase
  - Jweb_Guru 11y ago
    Kyle's point there is that it does matter, in that CouchDB can't achieve consensus, and would have failed Jepsen immediately.
deleted 11y ago
[deleted]

I really would like to see Couchbase analyzed... and for aphyr to marry me.

by MCRed 11y ago

I really would like to see Couchbase analyzed... and for aphyr to marry me.

I'm actually genuinely interested in that as well (Not the marrying part), especially considering aphyr and Damien Katz went at it about a year ago: https://twitter.com/damienkatz/status/527588456747499520 https://twitter.com/damienkatz/status/527588456747499520

willchen 11y ago
Educational back-and-forth, although unnecessarily biting. TL;DR - Aphyr thinks Damien Katz never read this: https://en.wikipedia.org/wiki/Consensus_%28computer_science%29#Problem_description https://en.wikipedia.org/wiki/Consensus_%28computer_science%...
augustl 11y ago
What I find really interesting is that while it appears to me that Katz has very sparse knowledge of databases, he has still managed to create one or two of them, and successfully run a company that sells one. I don't like the thought I had next, but: perhaps knowing about consensus algos and papers actually doesn't matter?
- Saavedro 11y ago
  well, matter for what? For building software that seems to work, sure, no. But for being able to speak to its capabilities -- or even know what they are, especially in the case of distributed systems it's definitely important. this is why so many of the new DB offerings have docs that are either misleading or wrong -- often the doc writers or even the devs themselves don't know what invariants their system can guarantee and assume several that it can't.
- DomreiRoam 11y ago
  Depends on the problem you want to solve. CouchDB is a very good document database when you have more read than write and when writer are mostly writing on different documents. If I understand correctly replication conflict resolution is up to the application. So knowing about consensus algo is unnecessary for CouchDB because he doesn't support it. I think it's smart to know a little about the literature; enough to know what battle you don't want to fight. It is not smart to try to develop an engine on the basis that it will need to beat the law of thermodynamic to be possible. But also, “They did not know it was impossible so they did it”, Mark Twain
  - krugster 11y ago
    FWIW, Couchbase != CouchDB: http://www.couchbase.com/couchbase-vs-couchdb http://www.couchbase.com/couchbase-vs-couchdb +1 For Jepson on Couchbase
- Jweb_Guru 11y ago
  Kyle's point there is that it does matter, in that CouchDB can't achieve consensus, and would have failed Jepsen immediately.

deleted 11y ago

[deleted]