Systems and methods for efficient scalability and high availability of applications in container orchestration cloud environment

Abstract

The disclosure provides efficient scalability and high availability of applications in a container orchestration cloud environment. A readiness orchestrator monitors the readiness of an application. Configuration data is managed by a configuration cache manger and can be stored locally or in a centralized database. The configuration for each subsystem is managed using a fully-qualified domain name (FQDN). The FQDN can be obtained using a Domain Name System (DNS) service. The load data of a content server (CS) subsystem and an independent Java method server (iJMS) subsystem are obtained and stored in the database. A helper pod is adapted for auto-scaling depending upon the load data and the configuration data of the CS subsystem and the iJMS subsystem to thereby maintain high availability of the CS subsystem and the iJMS subsystem in the container orchestration cloud environment.

What is claimed is: 
     
         1 . A method, comprising:
 obtaining, by a configuration cache manager locally from a configuration cache or directly from a database, configuration details for an instance of an application newly spawned in a container orchestration cloud environment, the configuration details comprising a configuration version number, the instance of the application comprising instance data, the instance data comprising a configuration version number;   validating, by the configuration cache manager, the configuration version number from the configuration details, wherein the validating comprises comparing the configuration version number from the configuration details with the configuration version number from the instance data; and   responsive to the configuration version number from the configuration details not matching the configuration version number from the instance data, updating the configuration details stored in the configuration cache, the database, or both with the configuration version number from the instance data.   
     
     
         2 . The method according to  claim 1 , further comprising:
 tracking a number of user requests for the application in the container orchestration cloud environment; and   dynamically spawning the instance of the application to accommodate the number of user requests.   
     
     
         3 . The method according to  claim 1 , further comprising:
 inquiring the database for a status of the instance periodically; and   updating the database in response to the instance being killed.   
     
     
         4 . The method according to  claim 1 , wherein the database stores configurations of instances of the application. 
     
     
         5 . The method according to  claim 4 , wherein the configurations are managed using hostnames. 
     
     
         6 . The method according to  claim 5 , wherein each of the hostnames is a fully-qualified domain name. 
     
     
         7 . The method according to  claim 1 , wherein the configuration cache is managed by the configuration cache manager. 
     
     
         8 . A system, comprising:
 a processor;   a non-transitory computer-readable medium; and   instructions stored on the non-transitory computer-readable medium and translatable by the processor for:
 obtaining, locally from a configuration cache or directly from a database, configuration details for an instance of an application newly spawned in a container orchestration cloud environment, the configuration details comprising a configuration version number, the instance of the application comprising instance data, the instance data comprising a configuration version number; 
 validating the configuration version number from the configuration details, wherein the validating comprises comparing the configuration version number from the configuration details with the configuration version number from the instance data; and 
 responsive to the configuration version number from the configuration details not matching the configuration version number from the instance data, updating the configuration details stored in the configuration cache, the database, or both with the configuration version number from the instance data. 
   
     
     
         9 . The system of  claim 8 , wherein the instructions are further translatable by the processor for:
 tracking a number of user requests for the application in the container orchestration cloud environment; and   dynamically spawning the instance of the application to accommodate the number of user requests.   
     
     
         10 . The system of  claim 8 , wherein the instructions are further translatable by the processor for:
 inquiring the database for a status of the instance periodically; and   updating the database in response to the instance being killed.   
     
     
         11 . The system of  claim 8 , wherein the database stores configurations of instances of the application. 
     
     
         12 . The system of  claim 11 , wherein the configurations are managed using hostnames. 
     
     
         13 . The system of  claim 12 , wherein each of the hostnames is a fully-qualified domain name. 
     
     
         14 . The system of  claim 8 , wherein the configuration cache is managed by a configuration cache manager. 
     
     
         15 . A computer program product comprising a non-transitory computer-readable medium storing instructions translatable by a processor for:
 obtaining, locally from a configuration cache or directly from a database, configuration details for an instance of an application newly spawned in a container orchestration cloud environment, the configuration details comprising a configuration version number, the instance of the application comprising instance data, the instance data comprising a configuration version number;   validating the configuration version number from the configuration details, wherein the validating comprises comparing the configuration version number from the configuration details with the configuration version number from the instance data; and   responsive to the configuration version number from the configuration details not matching the configuration version number from the instance data, updating the configuration details stored in the configuration cache, the database, or both with the configuration version number from the instance data.   
     
     
         16 . The computer program product of  claim 15 , wherein the instructions are further translatable by the processor for:
 tracking a number of user requests for the application in the container orchestration cloud environment; and   dynamically spawning the instance of the application to accommodate the number of user requests.   
     
     
         17 . The computer program product of  claim 15 , wherein the instructions are further translatable by the processor for:
 inquiring the database for a status of the instance periodically; and   updating the database in response to the instance being killed.   
     
     
         18 . The computer program product of  claim 15 , wherein the database stores configurations of instances of the application. 
     
     
         19 . The computer program product of  claim 18 , wherein the configurations are managed using hostnames. 
     
     
         20 . The computer program product of  claim 19 , wherein each of the hostnames is a fully-qualified domain name.