Jump to content
Welcome to our new Citrix community!
  • Turbo-charge App Performance with Application Delivery and Security Service

    Avinash Voona
    • Validation Status: Validated
      Summary: A new intent-based SaaS: App Delivery and Security Service, has been introduced that delivers applications with a high level of automation so that businesses can ensure the best user experience.
      Has Video?: No

    Latency is the mother of interactivity. Low Latency has become an indispensable part of communication, it is not an option anymore. The less interactive a site becomes the more likely users are to simply click away to a competitor’s site. So, to enhance user experience and improve application responsiveness and availability, the majority of web applications use Application Delivery Controllers / Load balancers.

    Application deployment and delivery can be complex in the cloud era and with so much at stake in terms of application experience, it needs to be made simpler and less error-prone. This new service is designed to be intent-based with unmatched automation so that businesses can deliver applications more quickly.

    When you intend to take a vacation and use the services of a travel agent, you tell the agent where you want to go and when, and the agent plans the itinerary, books plane tickets, and reserves accommodations. Similarly, App Delivery and Security Service enables you to define your business intent, translates that into the right policies, and then automatically orchestrates and configures resources appropriately to achieve it.

    App Delivery and Security Service removes the complexity from each step of the application delivery lifecycle. You simply define the intent and let the service take care of all the tedious, repetitive orchestration and configuration steps for you. The unmatched levels of automation increase operational efficiencies by up to 60 percent for IT. After all, IT should be focused on the business goals and not the syntax of the configuration.

    Below are the 3 major factors that contribute to the web page load time.

    • Client to ADC

    • ADC Processing

    • Server response time

    Let’s see how the service delivers the desired intent to ensure the best app performance and lower app latency throughout the year 

    Use Case 1: Ensure the best app performance and lower app latency throughout the year.

    To achieve the best app performance and the least latency, we follow a three-phased approach called Design, Deploy and Optimise.

    Design: The phase where you are preparing for app deployment in the cloud. When there is a dilemma to choose clouds, cloud regions based on the optimal cloud region to provide the least latency to end users.
    Here the Cloud Recommendation Engine of service helps.

    • Cloud recommendation engine:

    It recommends you the best locations to deploy new sites for a multi-site application. These recommendations help you boost the overall performance of your application.
    The recommendations provided are based on the user location, traffic (in percentage) expected from each user location, and the cloud service provider. You can use the recommended site location information while adding sites for a multi-site application.
    The cloud region recommendation engine provides recommendations for single-site, dual-site, and triple-site scenarios. The recommendations contain location information, global latency, and benefit percentage. Global latency is based on real-time measurements and the site location recommendations are arranged according to the best-performing combination of cloud providers’ sites. Benefit displays the advantage of choosing dual-site or triple-site in comparison with the single site.
    Let's suppose there is a global app called demo app 1, with 30% user traffic from each country United States, UK, India, and the rest 10% from other countries as shown in the screenshot below. Let’s see how the service provides recommendations to lower the end-user latency.


    App Delivery and Security service provide multiple recommendations with varying Global Latency, by comparing the latency benefit percentage across recommendations. As shown in the screenshot below, the Global latency for a single-site is 108.71ms, a dual-site is 65.09ms and a triple-site is 39.76ms. Customer/Admin based on the desired intent to keep the lower latency to end users will pick a triple site and bring their App servers to the recommended cloud regions.
    It also provides new cloud region recommendations to lower the end user latency for the already deployed apps by tracking user distribution per Geo and the respective latency.


    For more information on how to configure, see CADS Cloud region recommendation engine.

    Deploy: In the Deploy phase, as we know the optimal cloud regions the ADC Env will be deployed to seamlessly deliver and secure the applications, where the operational overhead of ADC Env is offloaded to us. The deployed ADC Env auto scales (scale up, scale down) based on the ADC resource utilization.

    Optimize: Once you have deployed the application and actual traffic is running. During the operations phase your traffic fluctuates, and the internet state changes, so it is more necessary to gauge and self-heal the root cause if there is an issue like a poor-performing server.
    Here the Self-healing of Service helps.

    • Self-healing

    The self-healing capability provides deep application analytics with improved application experience.
    With the self-healing capability:

    • You can automatically detect, remediate, and replace the defective server with a healthy server whenever the performance of an application server degrades or starts to malfunction.

    If an anomaly is detected in one of the instances of an application, it generates an alert and can automatically take remediation actions. The detected anomalies and corrective steps are logged inside the Action History.
    The service considers the following conditions while replacing a faulty server:

    • All persistent connections are honored.

    • Existing connections are completed.

    • New connections aren’t accepted for the faulty server.

          As shown in the above screenshot, enable Auto replace slow server to self-heal from bad performing/slow server.  For more information on how to configure, see Create Services.

    • Automatically replace Slow Server: In a stack of applications running as a back-end server in an Autoscale group, if one of the instances goes faulty. And if that instance starts responding slowly based on the response time. Then, the self-healing feature enables detecting the faulty server and replacing the faulty server with a healthy server automatically.

      To know more about App Delivery and Security service, register here


    User Feedback

    Recommended Comments

    There are no comments to display.

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

  • Create New...