A hybrid method of IPAAS + APAAS with front-end and back-end separation

Abstract

The application discloses to the technical field of software development architecture design, specifically a front-end and back-end separated ipaas+apaas mixed method, an iPaaS layer is connected with a business layer through an API interface, and the basic capability of the business layer and the customized interface capability developed by native code are integrated into a new complex scene interface through a scheduling engine downward; the new complex scene interface is connected with an iPaaS connector through API service to provide standardized interface capability for an aPaaS, and the aPaaS layer is used for building an application display layer, and a simple model-based design provides a simple scene business data operation interface for a front-end page, and the application integrates the API service platform, service scheduling capability of the iPaaS and the front-end page visual construction capability of the aPaaS to realize service of the basic capability of enterprise steady state, realize low-code and native code mixed development, and the architecture is decoupled.

Description

Technical Field

[0001] This application relates to the field of software development architecture design technology, specifically a hybrid method of front-end and back-end separation of ipaas and apaas. Background Technology

[0002] aPaaS: Application Platform as a Service. iPaaS: Integration Platform as a Service. JWT: JSON Web Token (JWT) is currently the most popular cross-domain authentication solution.

[0003] PaaS technology is currently relatively mature, and the market is experiencing rapid growth. aPaaS provides a rapid solution for building internal enterprise applications, while iPaaS is generally used to connect business and data flows between internal and external, cloud and on-premises business systems. Both products have their applicable scenarios, but they also have their own limitations. aPaaS platforms can quickly and visually build front-end interfaces, but they may encounter bottlenecks in complex business scenarios and high-performance interface implementations. iPaaS platforms are mainly responsible for connecting business and data flows between systems and typically do not directly interact with the front-end page. Enterprise digital transformation is also moving towards agility and service-oriented architecture, thus requiring a complete solution that integrates stable and agile software architectures. Summary of the Invention

[0004] The purpose of this application is to provide a hybrid iPaaS+apaas approach with front-end and back-end separation, in order to solve the problems mentioned in the background art, such as the bottleneck of aPaaS platform in complex business scenarios and high-performance interface implementation, and the problem that iPaaS platform does not directly interact with the front-end page.

[0005] To achieve the above objectives, this application provides the following technical solution: a front-end and back-end separated iPaaS+apaas hybrid method, including a business layer, an aPaaS layer, and an iPaaS layer, comprising the following steps:

[0006] Step 1: The iPaaS layer connects to the business layer through API interfaces. Downward, it integrates the basic capabilities of the business layer and the customized interface capabilities developed in native code into new complex scenario interfaces through the orchestration engine. Upward, it provides standardized interface capabilities for aPaaS by providing API services and connecting to the iPaaS connector.

[0007] Step 2: The aPaaS layer is used to build the application presentation layer. Based on a simple model design, it provides business data operation interfaces for simple scenarios for the front-end page. Through the standard service interface of iPaaS in Step 1, it realizes business data interaction for complex scenarios.

[0008] Preferably, in step 1, the access authentication of the iPaaS connector involves aPaaS using JWT to store user session information, and iPaaS being responsible for parsing the stored JWT into user-related information and placing it into the interface call context for use.

[0009] Preferably, the iPaaS connector authentication plugin configuration process includes the following steps:

[0010] S1: Select the connector and add connector authentication information, and set a unique identifier;

[0011] S2: Select the environment and authentication interface;

[0012] S3: Configure the authentication parameter acquisition method and the corresponding key;

[0013] S4: Configure verification rules;

[0014] The extension points reserved in S3 and S4 can implement replacement verification logic through self-encoding.

[0015] Preferably, the configuration process for the application-associated iPaaS connector authentication plugin includes the following steps:

[0016] Step A: Add an application and set the application interface access prefix. The unique rule is [custom part + tenant ID (tenant ID is encoded using code)]. The application access prefix must be added when accessing the interface.

[0017] Step B: Select authentication method: 1. Use connector authentication, select the corresponding connector authentication configuration; 2. No authentication required, no data permissions are checked, only the interface scope is verified; 3. Use access token authentication, obtain the token through appKey and secret.

[0018] Preferably, the interface authentication plugin process using the iPaaS connector includes the following steps:

[0019] 1. The front-end aPaaS layer uses the application prefix to call the interface and pass the authentication parameters to the iPaaS layer interface for execution;

[0020] 2. The iPaaS layer finds the application and authentication configuration based on the specified prefix, and uses the iPaaS connector authentication plugin to verify whether the authentication parameters are valid. If invalid, it outputs the response result directly. If valid, it checks whether there is permission to use the interface. If no permission is found, it outputs the response result directly. If permission is found, it executes the API and outputs the execution result.

[0021] Compared with the prior art, the beneficial effects of this application are:

[0022] This invention integrates the API service platform and service orchestration capabilities of iPaaS with the front-end page visualization construction capabilities of aPaaS. By service-orientedizing the enterprise's stable basic capabilities, and then orchestrating, integrating, and assembling new capabilities, it provides flexible service capability support for the front-end visualization page. It also solves the problem that aPaaS is difficult to implement complex business logic, and realizes a hybrid development of low-code and native code with mutual decoupling. Attached Figure Description

[0023] Figure 1 This is an architecture diagram of the business layer, aPaaS layer, and iPaaS layer of this application;

[0024] Figure 2 This is a flowchart illustrating an embodiment of this application;

[0025] Figure 3 Flowchart for configuring the connector authentication plugin in this application;

[0026] Figure 4 Flowchart for configuring the authentication plugin for the application-associated connector in this application;

[0027] Figure 5 Flowchart of the connector authentication plugin used for the interface of this application;

[0028] Figure 6 Add an orchestration API flowchart to this application;

[0029] Figure 7 This document presents a flowchart illustrating the API orchestration process for this application. Detailed Implementation

[0030] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0031] Example:

[0032] Please see Figure 1-7This application provides a technical solution: a hybrid method of front-end and back-end separation of iPaaS and aPaaS, including a business layer, an aPaaS layer and an iPaaS layer, comprising the following steps:

[0033] Step 1: The iPaaS layer connects to the business layer through API interfaces. Downward, it integrates the basic capabilities of the business layer and the customized interface capabilities developed in native code into new complex scenario interfaces through an orchestration engine. Upward, it provides standardized interface capabilities for aPaaS by providing API services and connecting to the iPaaS connector. The access authentication of the iPaaS connector is that aPaaS uses JWT to store user session information, and iPaaS is responsible for parsing the stored JWT into user-related information and putting it into the interface call context.

[0034] Step 2: The aPaaS layer is used to build the application presentation layer. Based on a simple model design, it provides business data operation interfaces for simple scenarios for the front-end page. Through the standard service interface of iPaaS in Step 1, it realizes business data interaction for complex scenarios.

[0035] by Figure 2 Taking a shopping mall's operational activities as an example, if a mall is preparing to run a multi-points promotion, customers who participate in the promotion can earn points based on the merchant's preset point multiplier by presenting their receipts. This application method integrates IPAAS and APAAS to provide flexible service capabilities for the front-end visual page.

[0036] like Figure 3 As shown, the iPaaS connector authentication plugin configuration process includes the following steps:

[0037] S1: Select the connector and add connector authentication information, and set a unique identifier;

[0038] S2: Select the environment and authentication interface;

[0039] S3: Configure the authentication parameter acquisition method and the corresponding key;

[0040] S4: Configure verification rules;

[0041] The extension points reserved in S3 and S4 can implement replacement verification logic through self-encoding.

[0042] like Figure 4 As shown, the configuration process for the application-associated iPaaS connector authentication plugin includes the following steps:

[0043] Step A: Add an application and set the application interface access prefix. The unique rule is [custom part + tenant ID (tenant ID is encoded using code)]. The application access prefix must be added when accessing the interface.

[0044] Step B: Select authentication method: 1. Use connector authentication, select the corresponding connector authentication configuration; 2. No authentication required, no data permissions are checked, only the interface scope is verified; 3. Use access token authentication, obtain the token through appKey and secret.

[0045] like Figure 5 As shown, the interface using the iPaaS connector authentication plugin process includes the following steps:

[0046] 1. The front-end aPaaS layer uses the application prefix to call the interface and pass the authentication parameters to the iPaaS layer interface for execution;

[0047] 2. The iPaaS layer finds the application and authentication configuration based on the specified prefix, and uses the iPaaS connector authentication plugin to verify whether the authentication parameters are valid. If invalid, it outputs the response result directly. If valid, it checks whether there is permission to use the interface. If no permission is found, it outputs the response result directly. If permission is found, it executes the API and outputs the execution result.

[0048] Figure 6 and Figure 7 To add an execution connector authentication operator (or simply use the connector operator directly, select the specified API, and only add an option when selecting the key, without needing key verification).

[0049] The foregoing has shown and described the basic principles, main features, and advantages of this application. It will be apparent to those skilled in the art that this application is not limited to the details of the exemplary embodiments described above, and that this application can be implemented in other specific forms without departing from the spirit or basic characteristics of this application. Therefore, the embodiments should be regarded as exemplary and non-limiting in all respects. The scope of this application is defined by the appended claims rather than the foregoing description. Therefore, it is intended to encompass all variations falling within the meaning and scope of equivalents of the claims within this application, and no reference numerals in the claims should be regarded as limiting the scope of the claims.

[0050] Although embodiments of this application have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and variations can be made to these embodiments without departing from the principles and spirit of this application, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A front-back end separated ipaas+apaas hybrid method, comprising a business layer, an aPaaS layer and an iPaaS layer, characterized in that: Comprise the following steps: Step 1: the iPaaS layer is connected with the business layer through an API interface, and the basic capabilities of the business layer and the customized interface capabilities developed by native code are integrated into new complex scenario interfaces through the orchestration engine; the new complex scenario interfaces are connected with the iPaaS connector through API service to provide standardized interface capabilities for aPaaS; Step 2: the aPaaS layer is used to build the application display layer, and the simple model-based design provides simple scenario business data operation interfaces for the front-end page, and through the standard service interface of the iPaaS in step 1, the business data interaction of the complex scenario is realized.

2. The front-back end separated ipaas+apaas hybrid method of claim 1, wherein: The access authentication of the iPaaS connector in step 1 stores user session information using JWT, and the iPaaS is responsible for parsing the stored JWT into user-related information and putting it into the interface call context for use.

3. The front-back separated ipaas+apaas hybrid method according to claim 1 or 2, characterized in that: The iPaaS connector authentication plug-in configuration process comprises the following steps: S1: select the connector and add the connector authentication information, set the unique identifier; S2: select the environment and authentication interface; S3: configure the authentication parameter acquisition method and the corresponding key; S4: configure the verification rule; The reserved extension points in S3 and S4 can replace the verification logic through self-coding.

4. The front-back end separated ipaas+apaas hybrid method of claim 3, wherein: The application-associated iPaaS connector authentication plug-in configuration process comprises the following steps: Step A: add the application and set the application interface access prefix, the unique rule is the custom part + tenant id, the tenant id uses code coding, and the application access prefix needs to be added when accessing the interface; Step B: select the authentication method: 1, use the connector authentication, select the corresponding connector authentication configuration; 2, no authentication, no data permission check, only interface range verification; 3, use access Token authentication, get token through appKey and secret.

5. The front-back end separated ipaas+apaas hybrid method of claim 4, wherein: The interface uses the iPaaS connector authentication plug-in process, which comprises the following steps: 1, the front-end aPaaS layer uses the application prefix to call the interface to pass the authentication parameters into the iPaaS layer interface execution; 2, the iPaaS layer finds the application and authentication configuration according to the specified prefix, uses the iPaaS connector authentication plug-in to verify whether the authentication parameters are valid, if it is judged invalid, directly output the response result, if it is judged valid, then verify whether there is interface use permission, if it is judged without permission, directly output the response result, if it is judged with permission, execute the API and output the return execution result.

Images