Home > Storage > ObjectScale and ECS > Product Documentation > ECS with Kemp LoadMaster Deployment Reference Guide > Overview
The explosive growth of unstructured data and cloud-native applications has created demand for scalable cloud storage infrastructure in the modern datacenter. ECS is the third-generation object store by Dell Technologies designed from the ground up to take advantage of modern cloud storage APIs and distributed data protection, providing active/active availability spanning multiple datacenters.
Managing application traffic both locally and globally can provide high availability (HA) and efficient use of ECS storage resources. HA is obtained by directing application traffic to known-to-be-available local or global storage resources. Optimal efficiency can be gained by balancing application load across local storage resources.
The ECS HDFS client, CAS SDK and ECS S3 API extensions are outside of the scope of this paper. The ECS HDFS client, which is required for Hadoop connectivity to ECS, handles load balancing natively.
Similarly, the Centera Software Development Kit for CAS access to ECS has a built-in load balancer. The ECS S3 API also has extensions leveraged by certain ECS S3 client SDKs which allow for balancing load to ECS at the application level.
Dell Technologies takes no responsibility for customer load balancing configurations. All customer networks are unique, with their own requirements. It is important for customers to configure their load balancers according to their own circumstance. We only provide this paper as a guide. Progress Kemp[1] or a qualified network administrator should be consulted before making any changes to your current load balancer configuration.