System and method for implementing a platform and language agnostic smart resiliency module

1. A method for automatically fixing health of a certain component of an application by utilizing one or more processors and one or more memories, the method comprising:

providing the application having a plurality of components required for running the application;

setting a corresponding predetermined threshold value for health of each corresponding component of the plurality of components of the application;

constantly monitoring health of the plurality of components;

when it is determined, in response to constantly monitoring, that the health of the certain component has reached to a value that is equal to the corresponding predetermined threshold value of the certain component, automatically calling corresponding application programming interface (API) to trigger the following automated processes:

collecting all necessary data corresponding to fixing of the health of the certain component related to the application from a plurality of data sources, wherein, in collecting all necessary data corresponding to the application, the method further comprising:

calling a private cloud API to access data from the private cloud related to the application;

calling a system of record API to access data from the system of record related to the application;

calling a load balancer API to access load balancer information data related to the application; and

calling a firewall API to access firewall information data related to the application;

creating a data file on demand that includes the necessary data; and

fixing the health of the certain component based on the data file.

2. The method according to claim 1 , further comprising:

creating the data file in any one of the following file formats: json, xml, and .yml.

3. The method according to claim 1 , wherein the threshold value indicates that the health of a corresponding component is still within an acceptable range necessary for running the application and that the corresponding component's health has not reached to a point to trigger the corresponding component's failure.

4. The method according to claim 1 , wherein, in constantly monitoring health of the plurality of components of the application, the method further comprising:

accessing data from a monitoring platform that allows real-time monitoring of the application;

accessing data from a suite of network management tools that allows monitoring of heterogeneous networks corresponding to running of the application;

accessing data from one central location hub that aggregates all data feeds with emergency information from various data sources to said one location hub corresponding to running of the application; and

accessing data from an event workflow platform related to running of the application.

5. The method according to claim 4 , wherein:

output data from the monitoring platform is input to the suite of network management tools;

output data from the suite of network management tools is input to said one central location hub;

output data from said one central location hub is input to the event workflow platform; and

output data from the event workflow platform is input to a platform and language agnostic resiliency module that automatically calls the corresponding API to trigger the automated processes of fixing the health of the certain component.

6. The method according to claim 1 , wherein, in fixing the health of the certain component based on the data file, the method further comprising:

inputting data from the data file to an application platform configured for building, testing, maintaining, and operating distributed applications with a blockchain backend; and

integrating output data from the application platform to a plurality of private clouds, distributed operating systems, databases, event workflow platform, open source platform configured for allowing users to seamlessly connect, manage and secure networks of different microservices regardless of platform, source or vendor.

7. A system for automatically fixing health of a certain component of an application, the system comprising:

a processor; and

a memory operatively connected to the processor via a communication interface, the memory storing computer readable instructions, when executed, causes the processor to:

set a corresponding predetermined threshold value for health of each corresponding component of a plurality of components of the application required for running the application;

constantly monitor health of the plurality of components;

when it is determined, in response to constantly monitoring, that the health of the certain component has reached to a value that is equal to the corresponding predetermined threshold value of the certain component, the processor automatically calls corresponding application programming interface (API) to trigger the following automated processes to:

collect all necessary data corresponding to fixing of the health of the certain component related to the application from a plurality of data sources, wherein, in collecting all necessary data corresponding to the application, the processor is further configured to:

call a private cloud API to access data from the private cloud related to the application;

call a system of record API to access data from the system of record related to the application;

call a load balancer API to access load balancer information data related to the application; and

call a firewall API to access firewall information data related to the application;

create a data file on demand that includes the necessary data; and

fix the health of the certain component based on the data file.

8. The system according to claim 7 , wherein the processor is further configured to:

create the data file in any one of the following file formats: json, xml, and -yml.

9. The system according to claim 7 , wherein the threshold value indicates that the health of a corresponding component is still within an acceptable range necessary for running the application and that the corresponding component's health has not reached to a point to trigger the corresponding component's failure.

10. The system according to claim 7 , wherein, in constantly monitoring health of the plurality of components of the application, the processor is further configured to:

access data from a monitoring platform that allows real-time monitoring of the application;

access data from a suite of network management tools that allows monitoring of heterogeneous networks corresponding to running of the application;

access data from one central location hub that aggregates all data feeds with emergency information from various data sources to said one location hub corresponding to running of the application; and

access data from an event workflow platform related to running of the application.

11. The system according to claim 10 , wherein:

output data from the monitoring platform is input to the suite of network management tools;

output data from the suite of network management tools is input to said one central location hub;

output data from said one central location hub is input to the event workflow platform; and

output data from the event workflow platform is input to a platform and language agnostic resiliency module that automatically calls the corresponding API to trigger the automated processes of fixing the health of the certain component.

12. The system according to claim 7 , wherein, in fixing the health of the certain component based on the data file, the processor is further configured to:

input data from the data file to an application platform configured for building, testing, maintaining, and operating distributed applications with a blockchain backend; and

integrate output data from the application platform to a plurality of private clouds, distributed operating systems, databases, event workflow platform, open source platform configured for allowing users to seamlessly connect, manage and secure networks of different microservices regardless of platform, source or vendor.

13. A non-transitory computer readable medium configured to store instructions for automatically fixing health of a certain component of an application, wherein, when executed, the instructions cause a processor to perform the following:

setting a corresponding predetermined threshold value for health of each corresponding component of a plurality of components of the application required for running the application;

constantly monitoring health of the plurality of components;

when it is determined, in response to constantly monitoring, that the health of the certain component has reached to a value that is equal to the corresponding predetermined threshold value of the certain component, wherein, when executed, the instructions further cause the processor to automatically call corresponding application programming interface (APJ) to trigger the following automated processes:

collecting all necessary data corresponding to fixing of the health of the certain component related to the application from a plurality of data sources, wherein, in collecting all necessary data corresponding to the application, the instructions, when executed, further cause the processor to perform the following:

calling a private cloud API to access data from the private cloud related to the application;

calling a system of record API to access data from the system of record related to the application;

calling a load balancer API to access load balancer information data related to the application; and

calling a firewall API to access firewall information data related to the application;

creating a data file on demand that includes the necessary data; and

fixing the health of the certain component based on the data file.

14. The non-transitory computer readable medium according to claim 13 , wherein, when executed, the instructions further cause the processor to perform the following:

creating the data file in any one of the following file formats: json, .xml, and .yml;

and wherein the threshold value indicates that the health of a corresponding component is still within an acceptable range necessary for running the application and that the corresponding component's health has not reached to a point to trigger the corresponding component's failure.

15. The non-transitory computer readable medium according to claim 13 , wherein, in constantly monitoring health of the plurality of components of the application, the instructions, when executed, further cause the processor to perform the following:

accessing data from a monitoring platform that allows real-time monitoring of the application;

accessing data from a suite of network management tools that allows monitoring of heterogeneous networks corresponding to running of the application;

accessing data from one central location hub that aggregates all data feeds with emergency information from various data sources to said one location hub corresponding to running of the application; and

accessing data from an event workflow platform related to running of the application.

16. The non-transitory computer readable medium according to claim 15 , wherein:

output data from the monitoring platform is input to the suite of network management tools;

output data from the suite of network management tools is input to said one central location hub;

output data from said one central location hub is input to the event workflow platform; and

output data from the event workflow platform is input to a platform and language agnostic resiliency module that automatically calls the corresponding API to trigger the automated processes of fixing the health of the certain component.

17. The non-transitory computer readable medium according to claim 13 , wherein, in fixing the health of the certain component based on the data file, the instructions, when executed, further cause the processor to perform the following:

inputting data from the data file to an application platform configured for building,

testing, maintaining, and operating distributed applications with a blockchain backend; and

integrating output data from the application platform to a plurality of private clouds, distributed operating systems, databases, event workflow platform, open source platform configured for allowing users to seamlessly connect, manage and secure networks of different microservices regardless of platform, source or vendor.