Load balancing Hitachi Content Platform
About Hitachi Content Platform
Hitachi Content Platform (HCP) is an object storage software solution that connects data producers, users, applications and devices into a central cloud storage platform. It allows IT organizations and cloud service providers to securely and cost-effectively store, share, protect, preserve and analyze data. The platform provides massive scale, multiple storage tiers, security, reliability, cloud capabilities, broad protocol support, multitenancy and configurable attributes for each tenant. HCP enables users to better understand, govern and control the degree of mobility of their data, as well as to identify insights and extract value for data-driven decisions and faster time to market.
Key benefits of load balancing
HCP has built-in load balancing capabilities but can also be deployed behind a load balancer. The load balancer is used to improve performance and resiliency by directing traffic to access nodes within an HCP cluster and to coordinate global traffic to multiple HCP clusters. The load balancer can also block unauthorized access by serving as the security boundary for an HCP cluster. Infrastructure featuring separate physical networks can leverage the load balancer to enable appropriate data access for HCP.
Here are a few key benefits:
- Ensures data is protected
- Helps make sure data is accessible at all times
- Enables businesses to meet growing data demands through scalability
How to load balance HCP
HCP architecture supports High Availability (HA) clustering by putting a load balancer in front of it.
For Hitachi Content Platform, using layer 7 SNAT mode is recommended. Layer 7 SNAT mode uses a proxy (HAProxy) at the application layer. Inbound requests are terminated on the load balancer and HAProxy generates a new corresponding request to the chosen Real Server. As a result, Layer 7 is not as fast as the Layer 4 methods. Layer 7 is typically chosen when either enhanced options such as SSL
termination, cookie based persistence, URL rewriting, header insertion/deletion etc. are required, or when the network topology prohibits the use of the layer 4 methods. Read the deployment brief for more details