Approaches for managing restrictions for middleware applications
Systems and methods are provided for determining an access request provided by an application that seeks to interact with one or more backend systems through a computing system. One or more predefined restrictions can be enforced on the application, the computing system, or the one or more backend systems.
1. A computer-implemented method, comprising:
processing, by a middleware application system, access requests provided by a first application and a second application running on respective first and second computing devices that interact with one or more backend systems through the middleware application system;
logging, in a first log, data generated from an interaction between the first application, the one or more backend systems, and the middleware application system;
logging, in a second log, data generated from an interaction between the second application, the one or more backend systems, and the middleware application system;
determining, by the middleware application system, data access restrictions associated with the first application and the second application; and
applying log data access restrictions to the first log and the second log that are commensurate with the determined data access restrictions.
2. The computer-implemented method of claim 1 , further including enforcing, by the middleware application system, one or more predefined restrictions that prevent continuous deployment of new and updated software in compliance with a software dependency matrix, wherein the software dependency matrix includes dependency information for software relied upon by the middleware application system.
3. The computer-implemented method of claim 1 , further including enforcing, by the middleware application system, one or more predefined restrictions that prevent modifications to data in compliance with a data dependency matrix, wherein the data dependency matrix includes dependency information for data relied upon by the application or the middleware application system.
4. The computer-implemented method of claim 1 , further including enforcing, by the middleware application system, one or more predefined restrictions that require the application to use a predefined software development kit (SDK) or software library.
5. The computer-implemented method of claim 1 , further including enforcing, by the middleware application system, one or more predefined restrictions that require the application to use a predefined library for service discovery.
6. The computer-implemented method of claim 1 , further including enforcing, by the middleware application system, one or more predefined restrictions that prevent the application from exceeding a predefined number of access requests to the one or more backend systems over a given period of time.
7. The computer-implemented method of claim 1 , further including enforcing, by the middleware application system, one or more predefined restrictions that prevent the middleware application system from sending an amount of data to the application in excess of a predefined amount.
8. The computer-implemented method of claim 1 , further including enforcing, by the middleware application system, one or more predefined restrictions that require the application to be identified in a list of applications that are permitted to interact with the middleware application system and the one or more backend systems.
9. The computer-implemented method of claim 1 , further including enforcing, by the middleware application system, one or more predefined restrictions that isolate logs generated based on interactions between the application, the middleware application system, and the one or more backend systems from logs generated based on interactions involving other applications.
10. A middleware application system, comprising:
one or more processors; and
a memory storing instructions that, when executed by the one or more processors, cause the middleware application system to perform:
processing access requests provided by a first application and a second application running on respective first and second computing devices that interact with one or more backend systems through the middleware application system;
logging, in a first log, data generated from an interaction between the first application, the one or more backend systems, and the middleware application system;
logging, in a second log, data generated from an interaction between the second application, the one or more backend systems, and the middleware application system;
determining, by the middleware application system, data access restrictions associated with the first application and the second application; and
applying log data access restrictions to the first log and the second log that are commensurate with the determined data access restrictions.
11. The system of claim 10 , wherein the instructions further cause the middleware application system to enforce one or more predefined restrictions that prevent continuous deployment of new and updated software in compliance with a software dependency matrix, wherein the software dependency matrix includes dependency information for software relied upon by the middleware application system.
12. The system of claim 10 , wherein the instructions further cause the middleware application system to enforce one or more predefined restrictions that prevent modifications to data in compliance with a data dependency matrix, wherein the data dependency matrix includes dependency information for data relied upon by the application or the middleware application system.
13. The system of claim 10 , wherein the instructions further cause the middleware application system to enforce one or more predefined restrictions that require the application to use a predefined software development kit (SDK) or software library.
14. The system of claim 10 , wherein the instructions further cause the middleware application system to enforce one or more predefined restrictions that require the application to use a predefined library for service discovery.
15. A non-transitory computer readable medium comprising instructions that, when executed, cause one or more processors of a middleware application system to perform:
processing access requests provided by a first application and a second application running on respective first and second computing devices that interact with one or more backend systems through the middleware application system;
logging, in a first log, data generated from an interaction between the first application, the one or more backend systems, and the middleware application system;
logging, in a second log, data generated from an interaction between the second application, the one or more backend systems, and the middleware application system;
determining, by the middleware application system, data access restrictions associated with the first application and the second application; and
applying log data access restrictions to the first log and the second log that are commensurate with the determined data access restrictions.
16. The non-transitory computer readable medium of claim 15 , wherein the instructions further cause the one or more processors of the middleware application system to enforce one or more predefined restrictions that prevent continuous deployment of new and updated software in compliance with a software dependency matrix, wherein the software dependency matrix includes dependency information for software relied upon by the middleware application system.
17. The non-transitory computer readable medium of claim 15 , wherein the instructions further cause the one or more processors of the middleware application system to enforce one or more predefined restrictions that prevent modifications to data in compliance with a data dependency matrix, wherein the data dependency matrix includes dependency information for data relied upon by the application or the middleware application system.
18. The non-transitory computer readable medium of claim 15 , wherein the instructions further cause the one or more processors of the middleware application system to enforce one or more predefined restrictions that require the application to use a predefined software development kit (SDK) or software library.
19. The non-transitory computer readable medium of claim 15 , wherein the instructions further cause the one or more processors of the middleware application system to enforce one or more predefined restrictions that require the application to use a predefined library for service discovery.