Today, we’re excited to announce Brightbox Cloud Balancers – our new distributed load balancing service which is available right now as part of the cloud beta programme.
Cloud Balancers make it effortless to add fault tolerance and horizontal scalability to your systems by distributing traffic across a pool of Cloud Servers – even within separate Zones.
If you’re already part of the cloud beta programme you’ll simply need to install the latest version of the CLI tool (0.10.1) and you’ll be able to create Cloud Balancers straightaway (see the documentation for instructions).
If you’re not on the beta programme and would like to be, why not submit a beta request today? :)
Cloud Balancers are managed via the Brightbox API (or using the CLI tool, which uses the API). You create a new balancer, specifying which services should be balanced and to which back end Cloud Servers. The Cloud Balancer is then automatically built, within a minute or so, on top of the Cloud Balancing layer which spans each Zone within a Region. You can then map a Cloud IP onto the balancer and traffic is distributed across your servers according to the policy you define (the default is “least connections”). The Cloud Servers are continuously monitored according to a “healthcheck” you specify. Should one of your Cloud Servers become unresponsive it is removed from the active pool of servers until it is “up” again.
Brightbox Cloud Balancers offer a number of advantages over Amazon’s ELB – here’s a few important ones…
We plan to announce pricing information on both this and other Brightbox Cloud services within the next month.
There will be a standard fixed hourly rate for each Cloud Balancer plus a charge for load balanced internet data (per GB).
Load Balancers are normally created and handling traffic within 90 seconds.
Exactly how much traffic a single balancer can handle depends largely on your application, but they can comfortably handle 6000 concurrent connections as standard. This will also increase dramatically in the near future as we add new scaling features to the Cloud Balancing layer.
You can balance most TCP-based protocols. Specifying an HTTP listener adds an “X-Forwarded-For” header.