from Hacker News

Application-Level Consensus [pdf]

by hugothefrog on 4/3/17, 7:52 AM with 8 comments

• by ergl on 4/3/17, 8:23 PM

  Jane Street uses the same approach to build their exchange [0]. Like the doc says, it can be great to replay some sequence of messages in dev to reproduce issues, and to give fault-tolerance to the system.

  One downside is that, if all your nodes are using the same application code, simply replaying the log might not help as all nodes might hit exactly the same bug with the same sequence of transitions.

  [0] There's an overwiev of their infrastructure here https://youtube.com/watch?v=b1e4t2k2KJY

• by gawi on 4/3/17, 1:12 PM

  This is very interesting. I have no doubts that not having to deal with fault tolerance at the application level compensates for the efforts to put in place this architecture. And yes, in my opinion, "application-level consensus" is the perfect term to designate this architecture.

• by silviatorres on 4/4/17, 1:46 PM

  Hi there!! looks like there was some minimal mistakes on the text and the document was updated: http://weareadaptive.com/wp-content/uploads/2017/04/Applicat...

• by eternalban on 4/3/17, 3:57 PM

  Try 'Edge-Coherence'.