Intelligent CIO Africa Issue 65 - Page 75

The main reason for this is that load balancers , which are used to front-end these applications , and make them accessible to end-users , were designed with monolithic applications in mind , and hence are unable to keep pace with the agile manner in which these cloud-native applications are deployed .
These load balancers were designed for a deployment process in which network resources for the applications are provisioned manually by network and security teams , a process that could take days if not weeks , and then manually configured on the load balancer . This process clearly inhibits achieving the goal of automation to which organisations aspire .
Further compounding this problem is the fact that when deploying applications in multi-cloud and hybrid cloud environments , each public cloud provider has its own custom load balancer and management system . For example , AWS has its own Elastic Load Balancing solution , which is different from Microsoft ’ s Azure Load Balancer . This makes the task of automating application deployment even more complex and time consuming . It also makes the task of applying a consistent set of policies across the different cloud environments more error prone as each load balancer has its own separate configuration .
To keep pace with cloud-native applications , one needs an application access solution that enables the
Having a solution that works consistently across the different cloud environments also provides the associated benefit of being able to apply a consistent set of policies for accessing the application , irrespective of the cloud in which it is running .
www . intelligentcio . com INTELLIGENTCIO AFRICA 75