84 lines
5.7 KiB
Markdown
84 lines
5.7 KiB
Markdown
# Load Balancers: Simplifying High Availability
|
||
|
||
- **期号**: SRE Weekly Issue #60（2017-02-20）
|
||
- **作者**: —
|
||
- **链接**: https://www.digitalocean.com/company/blog/load-balancers-simplifying-high-availability/
|
||
|
||
## 简介
|
||
|
||
I don’t often link to new product announcements, but DigitalOcean’s new Load Balancer product caught my attention. It looks to be squarely aimed at improving on Amazon’s ELB product.
|
||
|
||
## 正文
|
||
|
||
© 2026 DigitalOcean, LLC.[Sitemap](https://www.digitalocean.com/sitemap).
|
||
|
||
By Rafael Rosa
|
||
|
||
- Published:
|
||
- 3 min read
|
||
|
||
Over the past five years, we’ve seen our community grow by leaps and bounds, and we’ve grown right alongside it. More and more of our users are managing complex workloads that require more resilience and need to be highly available. Our [Reserved IPs](https://assets.digitalocean.com/blog/static/floating-ips-start-architecting-your-applications-for-high-availability/) already enable you to implement an architecture that eliminates single points of failure, but we knew we could do better by bringing our “DO-Simple” approach to the problem.
|
||
|
||
So today, we are releasing **Load Balancers**—a fully managed, highly available service that you can deploy as easily as a Droplet.
|
||
|
||
Our goal is to provide simple and intuitive tools that let your team launch, scale, and manage production applications of any size. With our Load Balancers, just choose a region and which Droplets will receive the traffic. We take care of the rest.
|
||
|
||
Load Balancers cost **$10/month** [note: edited November 5, 2018, from $20/month] with no additional bandwidth charges and are available in all DigitalOcean regions.
|
||
|
||
- Load balance TCP, HTTP, and HTTPS workloads within a specific DigitalOcean region.
|
||
- When using HTTPS, you can either terminate SSL on our Load Balancer or choose to use a passthrough mode.
|
||
- Choose your balancing algorithm and configure custom health checks, or use our defaults.
|
||
- Track Load Balancer usage and troubleshoot problems using the integrated graphs and metrics.
|
||
- Manage your Load Balancers using our web dashboard or [APIs](https://developers.digitalocean.com/documentation/v2/#load-balancers) .
|
||
|
||
For more details, see [this overview](https://www.digitalocean.com/community/tutorials/an-introduction-to-digitalocean-load-balancers) on our Community site.
|
||
|
||
Your Load Balancer will distribute incoming traffic across your Droplets, allowing you to build more reliable and performant applications by creating redundancy. You can add target Droplets to a Load Balancer by either choosing specific Droplets, or choosing a tag used by a group of Droplets.
|
||
|
||
With tags, scaling your application horizontally becomes easy. Launch a new Droplet with the tag applied, and it will be automatically added to your Load Balancer’s backend pool, ready to receive traffic. Remove the tag, and the Droplet will be removed from the backend pool.
|
||
|
||
|
||
|
||
|
||
Get started by following this [step-by-step guide](https://www.digitalocean.com/community/tutorials/how-to-create-your-first-digitalocean-load-balancer) on our Community site.
|
||
|
||
We didn’t forget about security! Here’s how Load Balancers’ measure up:
|
||
|
||
- HTTPS configuration that gives you [Grade A security](https://www.ssllabs.com/ssltest/analyze.html) out of the box.
|
||
- Uploaded SSL certificates are placed in a fully encrypted, isolated, and secure storage system.
|
||
- Load Balancer logs aren’t stored anywhere on our systems (only metrics for troubleshooting).
|
||
- Provisioning and operation of our Load Balancers is fully automated; there’s no human interaction.
|
||
|
||
If you’re configuring a Load Balancer instance to use SSL termination, keep in mind that any Droplet using Shared Private Networking connected to the Load Balancer will have traffic sent to its private IP. Otherwise, it will use the Droplet’s public IP. (For full control and end-to-end encryption, choose the “SSL passthrough” option.)
|
||
|
||
Learn more about configuring either [SSL termination](https://www.digitalocean.com/community/tutorials/how-to-configure-ssl-termination-on-digitalocean-load-balancers) or [SSL passthrough](https://www.digitalocean.com/community/tutorials/how-to-configure-ssl-passthrough-on-digitalocean-load-balancers) with our Community tutorials.
|
||
|
||
We already have many Load Balancer improvements planned. Some features you will see soon include:
|
||
|
||
- Support for Load Balancers in our [Ruby](https://github.com/digitalocean/droplet_kit) and[Go](https://github.com/digitalocean/godo) libraries as well as our command-line client,[doctl](https://github.com/digitalocean/doctl) .
|
||
- Integration with [Let’s Encrypt](https://letsencrypt.org/) for provisioning and deploying free TLS certificates with ease.
|
||
- Alerting on Load Balancer metrics with our upcoming [Monitoring](https://www.digitalocean.com/products/monitoring) solution.
|
||
- Improved integration with DNS records managed by DigitalOcean.
|
||
- Improved controls for rolling deployments.
|
||
- Load Balancers that work across nearby datacenters.
|
||
- IPv6 support.
|
||
|
||
Load Balancers are just the beginning. Our [2017 roadmap](https://blog.digitalocean.com/2017-whats-shipping-next-on-digitalocean/) is focused on bringing the “DO-Simple” experience to more complex, production workloads. Your feedback will help us as we improve Load Balancers and roll out more features, including new storage, security, and networking capabilities. Let us know what you think in the comments!
|
||
|
||
Rafael Rosa
|
||
|
||
Author
|
||
|
||
Krishna Nallamothu
|
||
|
||
- August 26, 2026
|
||
- 2 min read
|
||
|
||
Salman Paracha
|
||
|
||
- August 25, 2026
|
||
- 3 min read
|
||
|
||
- August 20, 2026
|
||
- 10 min read
|