Question
Can I use the DO load balancer solution to route based on region?
- Posted April 17, 2017
- Load Balancing
Right now, I’m using nginx to route calls to my API servers based on the region. So, if I have someone calling the API from the EU, it routes the request to the EU servers and if someone calls from the US, it routes to our US servers.
Is there a way to do this with the DO LB solution? I’d sure like to get away from managing our nginx server, if possible.
-Mark
Subscribe
Share
Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Sign in to AnswerThese answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Take a look at DNS Simple (my referral code - https://dnsimple.com/r/25d6ec942722a7 ) - We are using them for our DNS on the Professional plan for 25/month and they allow region based DNS records. It works like a charm and offers failover to alternate regions if there is an issue.
I would have loved the same. But as you’re after it I figured I’d point you to CloudFlare’s load balancer which is as they say ‘around the corner’ and supports this + a lot more: https://www.cloudflare.com/load-balancing/
@mkrieger
The DigitalOcean Load Balancers are very basic (as of this response) and only handle the basics, such as Round Robin, Least Connections, and Sticky Sessions (via a Cookie).
They are not yet configurable in a way that routes based on location using GeoIP or similar and there isn’t a way to configure them granularly as you would a custom instance.
This may change in the future since they are still relatively new. In the mean time, I’d recommend that you add the suggestion to the box by submitting a post to the feedback community.
That being said, from looking over the community, one of the biggest requests thus far is enabling support for HTTP/2 on the Load Balancers as they are still, from what I can see, using 1/1.1. That’s also something you can gain from a custom instance, such as what you’ve got and will lose if you switch (for now).
https://digitalocean.uservoice.com/forums/136585-digitalocean/suggestions/18267991-support-http-2-on-load-balancers