Live data from Hacker News

The Byzantine Generals Problem (1982) [pdf]

lamport.azurewebsites.net

21–22 of 22 posts

Re: The Byzantine Generals Problem (1982) [pdf]

#21
post #13

I agree with what James Mickens has to say about this area of expertise. Usually the thinking is to expect that things mostly work (which is wrong) and that in case of an inconsistency sending another message could fix it (which more often than not is also wrong). In an unreliable environment a new message might not arrive and even if it does it might not contain any meaningful information for the receiver as he can'…

Its funny how these tenets map out to relationships to humans. Replace messenger with "friend" and it still retains a measure of truth.

This is not a coincidence. I'm a worker node in a distributed international corp, and we have a lot of communication errors and timeouts, protocol errors and interpreter bugs, as well as byzantine generals called managers. Our kafka is called email and instead of kubernetes we sometimes use cubicles.

Re: The Byzantine Generals Problem (1982) [pdf]

#22
post #18
post #7

Earlier quoted context omitted.

Check out Hashgraph. It is asynchronous Byzantine.

Hashgraphs currently require a permissioned environment (eg. a node needs to know how many others there are and trust them to reach consensus) - so why not just use SQL Databases? They are even faster.

Pretty much all of BFT consensus protocols (like Paxos or Honey Badger) are like this, except SCP (Stellar). They are used e.g. in aviation, so they are very practical.
Post reply on HN