Skip to content
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

Anycast as a Load Balancing feature #16

Open
angelicagardner opened this issue Jan 10, 2025 · 0 comments · May be fixed by #17
Open

Anycast as a Load Balancing feature #16

angelicagardner opened this issue Jan 10, 2025 · 0 comments · May be fixed by #17

Comments

@angelicagardner
Copy link
Owner

Anycast as a Load Balancing feature

Author(s): Fernanda Weiden and Peter Frost
Link: https://dl.acm.org/doi/10.5555/1924976.1925002

Abstract

Our IT organization is made up of many sub-teams, each providing a service such as DNS, LDAP, HTTP proxy, and so on. Each one is deployed globally, using their own replication mechanisms. Our team provides Load Balancing and failover services in a way that other teams can use without having to manage the underlying technology. We recently added Anycast as a service we offer to other teams that need to be able to failover between Load Balancers. While Anycast is complex and mysterious to many systems administrators, our architecture provides the service in a way that the other teams do not need to worry about the details. They simply provide the service behind Load Balancers they currently use, with an additional virtual IP address. This paper describes how Anycast works, it's benefits, and the architecture we used to provide Anycast failover as a service.

DOI

10.5555/1924976.1925002

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

Successfully merging a pull request may close this issue.

1 participant