/explore
|
You are here 
|
muratbuffalo.blogspot.com | ||
| | | | |
jack-vanlightly.com
|
|
| | | | | This post continues my series looking at log replication protocols, within the context of state-machine replication (SMR) or just when the log itself is the product (such as Kafka). So far I've been looking at Virtual Consensus, but now I'm going to widen the view to look at how log replication protocols can be disaggregated in general (there are many ways). In the next post, I'll do a survey of log replication systems in terms of the types of disaggregation described in this post. | |
| | | | |
blog.schmizz.net
|
|
| | | | | The traditional way replicated systems are architected is to physically co-locate the write-ahead log (WAL) on the nodes where the state is being maintained. Then a consensus protocol like Paxos or Raft is used to make sure the log on each replica ag... | |
| | | | |
systemdesign.one
|
|
| | | | | scalable broadcast algorithm in distributed system | |
| | | | |
sookocheff.com
|
|
| | | The Network Time Protocol (NTP) is a system for synchronizing the clocks of hosts and clients across the Internet. NTP is a protocol intended to synchronize all computers participating in the network to within a few milliseconds of Coordinated Universal Time (UTC). The core of the protocol is NTP's clock discipline algorithm that adjusts the local computer's clock time and tick frequency in response to an external source - such as another trusted NTP server, a radio or satellite receiver, or a telephone modem. A core problem in NTP is establishing the trust and accuracy of nodes in the NTP network. This is done through a combination of selection and filtering algorithms to choose from the most reliable and accurate peer in the synchronization network. | ||
