New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Moving from master slave architechture to peer-peer #73841

Open
vikashiscoder opened this Issue Feb 8, 2019 · 2 comments

Comments

Projects
None yet
3 participants
@vikashiscoder
Copy link

vikashiscoder commented Feb 8, 2019

As the load of the controller increases it will not scale in a master slave setup of the clusters.
In case of peer to peer all nodes can respond as masters increasing the scaling capacity.

@neolit123

This comment has been minimized.

Copy link
Member

neolit123 commented Feb 10, 2019

please provide more detail about the feature you request.

/kind feature
/sig architecture

@vikashiscoder

This comment has been minimized.

Copy link
Author

vikashiscoder commented Feb 11, 2019

The master is the unified endpoint for the cluster. Single "source of truth" for the entire cluster. As load increases the capacity of master is exhausted. Also might lead to single point of failure.

When moving to peer to peer architecture, there is more scaling and no single point of failure. No single node or process is master. All can serve the requests based on their availability. More advantages can be added with implementation of gossip protocol in turn increasing the maintainability of nodes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment