Mission-critical web-based applications and workloads require high availability. Load balancing distributes workloads across two or more servers, network links, and other resources to maximize throughput, minimize response time and avoid overload. Rackspace cloud load balancers allow you to quickly load balance multiple Cloud Servers™ for optimal resource utilization.
Please see the pricing page for details. Standard charges for Cloud Files™ will apply if you have elected to enable log delivery to your Cloud Files account. Standard charges will apply for additional (unique) virtual IP addresses per load balancer.
Yes, implementation and management of our cloud load balancer solution is currently available through our Rackspace Cloud Control Panel and the API. In order to use our API, customers should have a general understanding of the load balancing service and be familiar with:
Yes, customers are able to utilize the RackConnect Cisco ASA solution to connect dedicated and cloud servers, while leveraging cloud load balancers to load balance between cloud servers. Customers utilizing RackConnect will be billed for outgoing bandwidth through their dedicated environment, as well as inbound and outbound traffic for their cloud load balancer.
If customers need to include dedicated and cloud servers in the same resource pools (to load balance between both platforms), they should leverage the RackConnect F5® BIG-IP® Local Traffic Manager™Solution.
Yes; however, we recommend using this service via RackConnect if you wish to include dedicated servers.
We do not currently recommend leveraging cloud load balancers with dedicated servers without RackConnect, except in low traffic scenarios (due to potential for significant bandwidth charges). Without RackConnect, you would be metered or billed for bandwidth charges for the request outbound from the cloud load balancer, the response outbound from their dedicated firewall, the response inbound to the cloud load balancer and the response outbound again from the cloud load balancer returning to the user.
A single load balancer is capable of handling 20,000 concurrent connections consistently with support for periodic spikes estimated at up to 100,000 concurrent connections. Cloud Load Balancers utilizes a multi-tenant environment; estimates are not guaranteed and may vary depending on the number of concurrent connections other customer load balancers are processing.
Each load balancer comes with one (1) public IPv4 address.
Yes via the API. SSL allows users to have their traffic terminate at the load balancer with centralized certificate management, SSL acceleration for improved throughput, reduced CPU load at the application server for better performance and HTTP/HTTPS session persistence.
Customers who have Personally Identifiable Information (PII) in their data. Examples of PII are HIPPA protected health information, Gramm-Leach-Bliley financial information, credit card information and any personal data that when disclosed could result in the theft of the person's identity.
In most cases, it should take less than one minute for a load balancer to be provisioned once the API request is submitted. During periods of extreme system load, we anticipate no more than a few minutes for complete provisioning.
A single cloud load balancer is connected via 10Gb/second network to both public and Rackspace's internal network, which we have tested to achieve about 9Gb/second of actual throughput. There are some limiting factors which may influence the actual throughput at any given time.
Customers who wish to modify their imposed API rate limits will need to contact Support.
Yes. For more information, check out the following link.
Try Cloud Load Balancers for yourself. Create a Rackspace Cloud account to get started.Sign Up Now