Resiliency for CI/CD Pipeline

The golden rule in IT is resiliency. The list of reasons to have a plan B is endless because breaches, hacks, unexpected traffic increases, and human error (to name a few) are a constant in the digital world. Building a resilient DevOps automation framework means the application delivery process can continue uninterrupted even when the unexpected occurs. 

HCL Launch 7.2.1 supports a resilient framework for disaster recovery in many ways. One of the biggest is a distributed front end server capability. As our customers grow in their DevOps adoption, the number of users logging into the HCL Launch Server continues to rise and with that additional activity comes more work load.

The distributed front-end server is a great way to spread around the user load and ensure that every user has a smooth experience within the UI. Adding these servers to your current environment builds in added resiliency by moving away from a single point of failure for your front end.

Below you will find the recommended approach for managing large volumes of traffic coming through your instances. End-user HTTP traffic can be routed through a load balancer, that can then be handed out to the distributed front end servers. This communication can optionally be pushed through another back end load balancer, or be delivered directly to the HCL Launch Servers.