One of the newest features we are very excited about for UrbanCode Deploy 7.0.3 is our Distributed Front End Server.
We don’t have to tell you that resiliency within your DevOps automation framework is important.
Having a framework that supports high availability and disaster recovery is critical to ensuring the continued success of your application delivery process. As our customers continue to grow their DevOps adoption, the number of users logging into the UrbanCode Deploy 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 not having a single point of failure for your front end.
Wondering where this fits with your current UCD setup? We thought you might!
Below you will find our 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 UrbanCode Deploy Servers.
Over the next couple of months, we will work to containerize the Distributed Front End Server allowing users to monitor their UrbanCode Deploy usage, and easily provision additional Front End Servers as needed.
Check back next week for more on the new features in UrbanCode Deploy 7.0.3.