talek
talek copied to clipboard
generalized followers
currently server/centralized.go
expects act as either a leader with a single follower, or as a follower.
We should at least generalize to support n
followers for single leader.
Right now it's set up for chaining. e.g. leader -> follower1 -> follower2 -> etc. any server can choose to terminate the chain.
Is that not sufficient?
it seems like conceptually it only needs to be
leader -> follower1 leader -> follower2 ...
that makes addition / replacement of followers easier since only one other node needs to change accounting (though it adds load to the leader, i suppose)
Sure, conceptually it's essentially a frontend gateway (that can coexist with any one of the servers). So the leader = follower + frontendGateway