skip to main content
Welcome to DataDirect Hybrid Data Pipeline : Deployment scenarios : Load balancer deployment
  

Try Now

Load balancer deployment

Hybrid Data Pipeline configuration depends in part on whether you are deploying the service on a standalone node or deploying the service on one or more nodes behind a load balancer. Deployment behind a load balancer offers high availability and scalability. For this reason, a load balancer deployment may be more suitable for a production environment, or for scenarios where the service must handle a high volume of traffic. In a load balancer deployment, the service is installed on one or more nodes behind a load balancer. Requests must be directed to the load balancer which forwards the request to the node, or, as in the case of a cluster, distributes requests across multiple nodes.
Important: There is currently no migration path from a standalone deployment to a load balancer deployment. Therefore, a standalone deployment is not recommended for environments where scaling up the service may be desired. A standalone node deployment is also not recommended for security and system recovery purposes. If you want to move from a test environment to a production environment, you should begin by deploying Hybrid Data Pipeline on a single node behind a load balancer. When deploying the service on a single node behind a load balancer, you can increase availability and scalability as demanded, and address security and recovery concerns as required.
Hybrid Data Pipeline is largely configured during the installation process. When installing the service on multiple nodes behind a load balancer, the initial installation of the Hybrid Data Pipeline server is used as a template for installations on additional nodes. The following configuration details should be addressed before installation to ensure a successful load balancer deployment.
*Login credentials for load balancer deployment
Passwords for the default administrator and user accounts must be specified during installation of the Hybrid Data Pipeline server. When initially logging in to the Web UI or using the API, you must authenticate as one of these users.
*Load balancer configuration
Hybrid Data Pipeline can be deployed on one or more nodes behind a load balancer to provide high availability and scalability. Hybrid Data Pipeline supports two types of load balancers.
*Network load balancers that support the TCP tunneling protocol (such as HAProxy)
*Cloud load balancers that support the WebSocket protocol (such as the AWS application load balancer and the Azure application gateway)
*System database for load balancer deployment
A system database is required for storing user and configuration information. For load balancer deployments, an external database is required to serve as the system database. As a best practice, the external system database should be replicated, or mirrored, to promote the continuous availability of the service.
*Shared files and the key location for load balancer deployment
The specification of a key location is required during installation. The installation program writes shared files used in the operation of the data access service to this directory. As a matter of best practices, the key location should be secured on a machine separate from the machines hosting the Hybrid Data Pipeline service or the machine hosting the system database. In the case of system failure, the backup files can be used to restore the service.
*Access ports for load balancer deployment
The access ports used for Hybrid Data Pipeline should be enabled for incoming traffic and unallocated for other purposes.
*SSL certificates for load balancer deployment
While end-to-end SSL/TLS communication is not supported for load balancer deployments of Hybrid Data Pipeline, SSL encrypted communications between clients and the load balancer are supported. In this scenario, the load balancer provides SSL termination to support encrypted communications.
*Application and driver configuration for load balancer deployment
Applications and drivers must be properly configured to ensure a successful deployment of the service.
*Browser configuration for load balancer deployment
For load balancer deployments, the browser you use to connect to the Web UI must be configured to echo cookies for session affinity. Most browsers echo cookies by default.
* Login credentials for load balancer deployment
* Load balancer configuration
* System database for load balancer deployment
* Shared files and the key location for load balancer deployment
* Access ports for load balancer deployment
* SSL certificates for load balancer deployment
* Application and driver configuration for load balancer deployment
* Browser configuration for load balancer deployment