31
Loadbalancing between 2 locations
(lemmy.dbzer0.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 10 Nov 2024
31 points (97.0% liked)
Selfhosted
40313 readers
264 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
Your challenge is that you need a loadbalancer. By hosting the loadbalancer yourself (e.g. on a VPS), you could also host your websites directly there...
My approach would be DNS-based. You can have multiple DNS A records, and the client picks one of them. With a little script you could remove one of the A Records of that server goes down. This way, you wouldn't need a central hardware.
Where would you host the script? If it's expected that the server that fires it off is always online and performing health checks, why not have it host a load-balancer? Or another local instance of the website? It's something fun to play around with, but if this is for anything beyond a fun exercise there are much better ways to accomplish this.
I'd host it on both webservers. The script sets the A record to all the servers that are online. Obviously, the script als has to check it's own service.
It seems a little hacky though, for a business use case I would use another approach.
That's an interesting idea, need to check if they offer some kind of a API for that.
But then there is this other thing, what about dns cache?
Set the DNS cache time to 60 seconds.
Set the script to run on every host delayed by some time to avoid simultaneously accessing the API (e.g. run the script every other minute).
With this approach, you get automatic failover in at most 3 minutes.