Integrating applications using containerized integration flow

Abstract

Techniques for integrating applications using a container image of an integration flow are disclosed. In some embodiments, a computer system performs operations comprising: providing a low-code no-code (LCNC) development platform to a computing device, the LCNC development platform being configured to enable a user to develop an integration flow; receiving a configuration of the integration flow from the computing device via the LCNC development platform, the integration flow being configured to enable communication between a first application being hosted on a first system and a second application being hosted on a second system; building a container image of the integration flow based on the configuration of the integration flow, the container image being configured to execute the integration flow; and deploying the container image of the integration flow on the second system, the deployed container image of the integration flow enabling communication between the first application and the second application.

What is claimed is: 
     
         1 . A system of comprising:
 at least one hardware processor; and   a non-transitory computer-readable medium storing executable instructions that, when executed, cause the at least one hardware processor to perform operations comprising:   receiving a configuration of an integration flow and an indication of defined messaging endpoints from a computing device, the integration flow defining a plurality of steps but not defining an application on which the plurality of steps are to be performed, the plurality of steps being configured to enable communication between a first application being hosted on a first system and a second application being hosted on a second system, wherein the second system is separate and distinct from the first system, the configuration created by a user via a graphical user interface (GUI) in which steps of the integration flow are dragged and dropped to define messaging endpoints and processing steps between messaging endpoints, wherein the messaging endpoints are the first application and the second application;   building a container image of the integration flow and indication of defined messaging endpoints based on the configuration of the integration flow, the container image being configured to execute the integration flow and coordinate input and output to the defined messaging endpoints;   deploying the container image of the integration flow on the second system, the deployed container image of the integration flow enabling communication between the first application and the second application; and   running the container image of the integration flow on the second system, the running of the container image of the integration flow comprising:   mapping the first application to the second application;   setting an authorization to enable the second system to obtain a payload of a request from the first application; and   executing the steps in coordination with the defined messaging endpoints.   
     
     
         2 . The system of  claim 1 , wherein the receiving of the configuration of the integration flow from the computing device comprises receiving the configuration of the integration flow via a low-code no-code (LCNC) development platform, the LCNC development platform being configured to enable a user of the computing device to develop the integration flow by using a graphical user interface (GUI) of the LCNC development platform to drag and drop components of the integration flow. 
     
     
         3 . The system of  claim 1 , wherein the first system has a first data model and the second system has a second data model that is different from the first data model. 
     
     
         4 . The system of  claim 1 , wherein the building the container image of the integration flow comprises generating a Java Archive (JAR) file. 
     
     
         5 . The system of  claim 1 , wherein the first application comprises an on-premise application being hosted on an on-premise system and the second application comprises a cloud application being hosted on a cloud system. 
     
     
         6 . The system of  claim 1 , wherein the first application comprises a first on-premise application being hosted on a first on-premise system and the second application comprises a second on-premise application being hosted on a second on-premise system. 
     
     
         7 . The system of  claim 1 , wherein the first application comprises a first cloud application being hosted on a first cloud system and the second application comprises a second cloud application being hosted on a second cloud system. 
     
     
         8 . The system of  claim 1 , wherein the running of the container image of the integration flow further comprises:
 converting the payload of the request, from the first application, from a first data format of the first application to a second data format of the second application; and   performing a network call to the second application using the converted payload of the request.   
     
     
         9 . A computer-implemented method performed by a computer system having a memory and at least one hardware processor, the computer-implemented method comprising:
 receiving a configuration of an integration flow and an indication of defined messaging endpoints from a computing device, the integration flow defining a plurality of steps but not defining an application on which the plurality of steps are to be performed, the plurality of steps being configured to enable communication between a first application being hosted on a first system and a second application being hosted on a second system, wherein the second system is separate and distinct from the first system, the configuration created by a user via a graphical user interface (GUI) in which steps of the integration flow are dragged and dropped to define messaging endpoints and processing steps between messaging endpoints, wherein the messaging endpoints are the first application and the second application;   building a container image of the integration flow and indication of defined messaging endpoints based on the configuration of the integration flow, the container image being configured to execute the integration flow and coordinate input and output to the defined messaging endpoints;   deploying the container image of the integration flow on the second system, the deployed container image of the integration flow enabling communication between the first application and the second application; and   running the container image of the integration flow on the second system, the running of the container image of the integration flow comprising:   mapping the first application to the second application;   setting an authorization to enable the second system to obtain a payload of a request from the first application; and   executing the steps in coordination with the defined messaging endpoints.   
     
     
         10 . The computer-implemented of  claim 9 , wherein the receiving of the configuration of the integration flow from the computing device comprises receiving the configuration of the integration flow via a low-code no-code (LCNC) development platform, the LCNC development platform being configured to enable a user of the computing device to develop the integration flow by using a graphical user interface (GUI) of the LCNC development platform to drag and drop components of the integration flow. 
     
     
         11 . The computer-implemented method of  claim 9 , wherein the first system has a first data model and the second system has a second data model that is different from the first data model. 
     
     
         12 . The computer-implemented method of  claim 9 , wherein the building the container image of the integration flow comprises generating a Java Archive (JAR) file. 
     
     
         13 . The computer-implemented method of  claim 9 , wherein the first application comprises an on-premise application being hosted on an on-premise system and the second application comprises a cloud application being hosted on a cloud system. 
     
     
         14 . The computer-implemented method of  claim 9 , wherein the first application comprises a first on-premise application being hosted on a first on-premise system and the second application comprises a second on-premise application being hosted on a second on-premise system. 
     
     
         15 . The computer-implemented method of  claim 9 , wherein the first application comprises a first cloud application being hosted on a first cloud system and the second application comprises a second cloud application being hosted on a second cloud system. 
     
     
         16 . The computer-implemented method of  claim 9 , wherein the running of the container image of the integration flow further comprises:
 converting the payload of the request, from the first application, from a first data format of the first application to a second data format of the second application; and   performing a network call to the second application using the converted payload of the request.   
     
     
         17 . A non-transitory machine-readable storage medium tangibly embodying a set of instructions that, when executed by at least one hardware processor, causes the at least one hardware processor to perform operations comprising:
 receiving a configuration of an integration flow and an indication of defined messaging endpoints from a computing device, the integration flow defining a plurality of steps but not defining an application on which the plurality of steps are to be performed, the plurality of steps being configured to enable communication between a first application being hosted on a first system and a second application being hosted on a second system, wherein the second system is separate and distinct from the first system, the configuration created by a user via a graphical user interface (GUI) in which steps of the integration flow are dragged and dropped to define messaging endpoints and processing steps between messaging endpoints, wherein the messaging endpoints are the first application and the second application;   building a container image of the integration flow and indication of defined messaging endpoints based on the configuration of the integration flow, the container image being configured to execute the integration flow and coordinate input and output to the defined messaging endpoints;   deploying the container image of the integration flow on the second system, the deployed container image of the integration flow enabling communication between the first application and the second application; and   running the container image of the integration flow on the second system, the running of the container image of the integration flow comprising:   mapping the first application to the second application;   setting an authorization to enable the second system to obtain a payload of a request from the first application; and   executing the steps in coordination with the defined messaging endpoints.   
     
     
         18 . The non-transitory machine-readable storage medium of  claim 17 , wherein the receiving of the configuration of the integration flow from the computing device comprises receiving the configuration of the integration flow via a low-code no-code (LCNC) development platform, the LCNC development platform being configured to enable a user of the computing device to develop the integration flow by using a graphical user interface (GUI) of the LCNC development platform to drag and drop components of the integration flow. 
     
     
         19 . The non-transitory machine-readable storage medium of  claim 17 , wherein the first system has a first data model and the second system has a second data model that is different from the first data model. 
     
     
         20 . The non-transitory machine-readable storage medium of  claim 17 , wherein the running of the container image of the integration flow further comprises:
 converting the payload of the request, from the first application, from a first data format of the first application to a second data format of the second application; and   performing a network call to the second application using the converted payload of the request.