Why DigitalOcean Load Balancing service is so expensive?

Posted May 3, 2018 16.3k views
UbuntuLoad Balancing

DigitalOcean charge $20/mo for Load Balancer, in my opinion it’s overprice, i mean we can buy $5 droplet and install nginx and configure our own load Balancer, what is special offer DigitalOcean give for $20 Load Balancer?

These 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.

Submit an Answer
7 answers

Any reason why the LB does not allow setting of a floating IP or even a CNAME to ensure updates to the infrastructure don’t end up requiring a DNS update ?

Since I arrived here from Google Search and it is the first result I hit, I wanted to add an update for anyone coming here too.

The cost of this service is ½ the cost it was previously and is only $10 a month per load balancer node.

Additionally, all traffic is free and each load balancer node can handle 10,000 connections at a time.

I would argue it may make sense to utilize this as a an initial ingress load balancer and then add your own application load balancer on top as needed.

There are a few reasons why a DO load balancer is more expensive than a $5 droplet…

  • DO load balaners include all bandwidth that passes through them in the $20 cost.

  • DO load balancers are a managed service. Our team manages the infrastructure required to ensure they work properly and are stable.

Creating your own load balancers is absolutely an option if you are willing to trade off the lower cost for the higher effort of installing, configuring, monitoring, and managing your load balancer and don’t expect your bandwidth use to go beyond what is included with your droplets.

¡Hi @kyawkyawsoezhu !
I think the load balancer cost is “the just price for the just service”. With Nginx you need make all manually. The load balancer is automatic. I think for critical cases the automatization is all you need.

Digital Ocean load balancer is the product for your “enterprise” products or SAAS.

Tyler here, Product Manager for Load Balancers. I’d also add to Ryan’s answer that as part of the managed Load Balancer service, it’s also a redundant and highly available service whereas your single $5 Droplet could go down, causing your backend Droplets to also become unavailable.

If this isn’t crucial to your application, along with some of the other features, you’re right that a custom solution on your own Droplet may be a good fit too.

Keep a look out for some new improvements to the service very shortly! (sooner rather than later....)

I know this is an old thread, but the Nginx LB and the DO LB are not apples to apples. The DO LB is a network/cloud LB, operating at the third and/or fourth layer of the OSI Reference Model. The Nginx LB would be operating at the application level, a significant difference in capabilities and use cases (at least in a production environemnt for the latter)

  • **The DO LB is a network/cloud LB, operating at the third and/or fourth layer of the OSI Reference Model.

    Do you have any evidence to back this claim? I think DO LB is haproxy.
    ****HAProxy is used as a component of DigitalOcean’s Load Balancer-as-a-Service product.

    • I wasn’t suggesting they are using Nginx, the link was for information only. What you sent seems to show what DO are using internally as well as for some of their product offerings. So it seems they are using HAProxy for their load balancing service.

      The load balancer service they offer is a network load balancer, as can be seen from the docs, ( see the second paragraph under “Protocol Support”. It wouldn’t make sense for them as an infrastructure provider to not have a network load balancer as an option. If you’re using their managed k8s service, you can also make use of HAProxy at the application level, but you also have the option to install other load balancers from their marketplace or manually.

Don’t know what do you mean by “network load balancer”. You are using vague terminology with no reference.