Load balancing Cloudian HyperStore S3 Object Storage

How to load balance Cloudian HyperStore

The load balancer sits in front of multiple HyperStore nodes. Four virtual services are used to load balance the different aspects of HyperStore:

• CMC – for Cloudian Management Console requests
• S3-HTTP – handles requests from S3 client applications via HTTP.
• S3-HTTPS – handles requests from S3 client applications via HTTPS.
• API – handles APO requests via HTTPS.

Single site scenario

In a single site scenario, multiple HyperStore nodes and two load balancers (configured as a high-availability pair) are deployed to ensure redundancy. Clients access the HyperStore nodes via the virtual IP address (VIP)

Multi site scenario

Under normal conditions, each site works as described in the single site scenario. Should all HyperStore nodes in one site become inaccessible, local client traffic is routed to the virtual IP address presented in the other site.

External clients can either be bound to a particular site, or to protect against site failure, the load balancer’s built-in global server load balancer (GSLB) can be leveraged to provide intelligent DNS name resolution & site connectivity.

Why Loadbalancer.org and Cloudian

Cloudian and Loadbalancer.org both specialize in reducing infrastructure complexity through intelligently designed and infinitely scalable network architecture. Users across many industries – including medical and media – are facing rapid increases in data, with storage demands intensifying as technologies progress.

The Cloudian and Loadbalancer.org partnership offers an answer to this challenge. Customers can enjoy the benefits of object storage in their own data centers, thanks to indestructible, enterprise, scale-out solutions.