CN114115841A

CN114115841A - Method, apparatus, device, medium and program product for dynamically arranging data stream interface

Info

Publication number: CN114115841A
Application number: CN202110362422.3A
Authority: CN
Inventors: 夏令
Original assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Wodong Tianjun Information Technology Co Ltd
Current assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Wodong Tianjun Information Technology Co Ltd
Priority date: 2021-04-02
Filing date: 2021-04-02
Publication date: 2022-03-01

Abstract

The application provides a dynamic arrangement method, a device, equipment, a medium and a program product of a data stream interface, wherein each service atom module is copied to a module assembly interface from a graphical module library by responding to a dragging instruction at the front end, then each service atom module is assembled into a target service module by responding to a logic assembly instruction, and an analysis request of the data stream interface is determined according to the target service module and preset interface parameters and is sent to the rear end; and determining an interface original file at the back end according to the received analysis request and a preset dynamic template, then dynamically compiling the interface original file according to the application environment of the interface, packaging the compiling result by using an interface packaging device, and determining a target data stream interface. The method realizes that interface core logic is constructed by utilizing a graphical front-end system, and then the interface code package is automatically and dynamically arranged by utilizing a back-end service system, so as to solve the technical problem of low development efficiency caused by developing the interface by relying on direct code customization in the prior art.

Description

Method, apparatus, device, medium and program product for dynamically arranging data stream interface

Technical Field

The present application relates to the field of computer data processing, and in particular, to a method, an apparatus, a device, a medium, and a program product for dynamically arranging a data stream interface.

Background

With the continuous development of internet technology, the requirement of new building or update maintenance of the application program is increasing, and the workload of the developer is also increasing, wherein especially the development of the interface between the front-end system and the back-end service system is rather heavy and repetitive work of the developer.

At present, the development of an Interface, i.e. an API (Application Programming Interface), is realized by directly writing related bearing codes according to the requirements and understanding of a specification of a requirement specification of an Application program by a developer. I.e., by taking customized development for a particular front-end application and back-end service system.

However, since a lot of repeated code editing work exists in a code customization development mode, developers cannot separate core logic of the interface from code editing, and the technical problem of low interface development efficiency is caused.

Disclosure of Invention

The application provides a dynamic arrangement method, a device, equipment, a medium and a program product of a data stream interface, which construct interface core logic by using a graphical front-end system and automatically dynamically arrange code program encapsulation corresponding to the interface according to the interface core logic by using a back-end service system so as to solve the technical problem of low development efficiency caused by developing the interface by relying on direct code customization in the prior art.

In a first aspect, the present application provides a method for dynamically arranging a data stream interface, which is applied to a backend service system, and includes:

receiving an analysis request sent by a front-end system;

determining an interface original file according to the analysis request and a preset dynamic template;

dynamically compiling the interface original file according to the application environment indicated in the analysis request to determine a compiling result, wherein the application environment is a platform environment used by a target data stream interface, and the target data stream is used for data interaction between a front-end system and a back-end service system;

and determining a target data stream interface according to the compiling result by using an interface wrapper.

In a possible design, the determining an interface source file according to the parsing request and a preset dynamic template includes:

determining a mapping protocol string and a preset interface parameter according to the analysis request;

resolving the mapping protocol string according to the preset interface parameters and the preset data protocol to determine each interface unit;

pre-reading a preset dynamic template, and adding an interface method unit in the preset dynamic template into an interface unit to determine an interface original file, wherein the method unit comprises the following steps: interface request mode, access path specification and method declaration.

In one possible design, the dynamically compiling the interface raw file according to the application environment indicated in the parsing request to determine a compiling result includes:

determining a corresponding compiler according to the application environment;

and dynamically compiling the interface original file by using a compiler, and loading an environment unit related to the application environment to the interface original file to determine a compiling result.

In one possible design, the dynamically compiling the interface raw file by using the compiler and loading an environment unit related to an application environment to the interface raw file to determine a compiling result includes:

determining a file management instance according to a compiler;

loading the environment unit into a file management instance, and constructing a compiling task instance through the file management instance;

performing compilation on the task instance to determine a compilation result.

In one possible design, before loading the environment unit into the file management instance, the method further includes:

creating an interface unit loader according to a context module of a current thread;

constructing a source file example according to the compiling unit name of the interface original file;

adding the source file instance to the file management instance using the interface unit loader;

correspondingly, the loading of the environment unit into the file management instance comprises the following steps:

the environment unit is loaded into the file management instance using an interface unit loader.

In one possible design, the determining, by the interface wrapper, the target data stream interface according to the compilation result includes:

determining a request-to-process mapper based on an application context module of an interface wrapper;

determining corresponding interface method units according to the compiling result;

screening out a target method unit annotated as a request mapper from each interface method unit according to the request-processing mapper;

and registering a target data stream interface by using the dynamic proxy module according to the compiling result and the target method unit.

Optionally, after determining each corresponding interface method unit according to the compiling result, the method further includes:

and setting the private attribute of the interface method unit as the visible attribute.

In one possible design, the method for dynamically arranging the data stream interface further includes:

and returning the target data stream interface to the front-end system.

In a second aspect, the present application provides a method for dynamically arranging a data stream interface, which is applied to a front-end system, and includes:

in response to a dragging instruction of a user, copying each service atom module from the graphical module library to a module assembly interface, wherein the service atom module is a graphical module formed by organizing service logic according to a preset format;

responding to a logic assembly instruction of a user, and assembling all the service atomic modules into a target service module;

determining an analysis request of a data stream interface according to a target service module and preset interface parameters;

and sending an analysis request to the back-end service system so that the back-end service system performs dynamic analysis according to the analysis request and determines a target data stream interface.

In a possible design, the determining an analysis request of a data stream interface according to a target service module and a preset interface parameter includes:

determining a mapping protocol string according to the target service module and a preset data protocol, wherein the mapping protocol string is used for representing each service atomic module and a service logic relationship between the service atomic modules;

and determining an analysis request according to the mapping protocol string and the preset interface parameter.

In one possible design, the determining a mapping protocol string according to the target service module and a preset data protocol includes:

and establishing a mapping relation between each service atomic module in the target service module and the corresponding service logic according to a format of a preset data protocol so as to determine a mapping protocol string.

Optionally, the preset data protocol is a JSON protocol, and the establishing a mapping relationship between each service atomic module in the target service module and the corresponding service logic according to a format of the preset data protocol to determine a mapping protocol string includes:

transmitting the target business module to a back-end service system;

the back-end service system is mapped into a JSON text according to each service atomic module and corresponding service logic according to a JSON protocol;

and determining a mapping protocol string according to the JSON text.

In a third aspect, the present application provides a dynamic arrangement apparatus for data stream interfaces, including:

the receiving module is used for receiving an analysis request sent by a front-end system;

the request processing module is used for determining an interface original file according to the analysis request and a preset dynamic template;

the compiling module is used for dynamically compiling the interface original file according to the application environment indicated in the analysis request so as to determine a compiling result, wherein the application environment is a platform environment used by a target data stream interface, and the target data stream is used for data interaction between the front-end system and the back-end service system;

and the packaging module is used for determining the target data stream interface according to the compiling result by using an interface packaging device.

In a possible design, the request processing module is configured to determine an interface source file according to an analysis request and a preset dynamic template, and includes:

the request processing module is used for determining a mapping protocol string and a preset interface parameter according to the analysis request;

the request processing module is also used for analyzing the mapping protocol string according to the preset interface parameters and the preset data protocol so as to determine each interface unit;

the request processing module is further configured to pre-read a preset dynamic template, and add an interface method unit in the preset dynamic template to the interface unit to determine an interface original file, where the method unit includes: interface request mode, access path specification and method declaration.

In one possible design, the compiling module is configured to dynamically compile the interface raw file according to an application environment indicated in the parsing request to determine a compiling result, and includes:

the compiling module is used for determining a corresponding compiler according to the application environment;

and the compiling module is also used for dynamically compiling the interface original file by utilizing the compiler and loading an environment unit related to the application environment to the interface original file so as to determine a compiling result.

In one possible design, the compiling module is further configured to dynamically compile an interface raw file by using a compiler, and load an environment unit related to an application environment to the interface raw file to determine a compiling result, including:

the compiling module is also used for determining a file management example according to the compiler;

the compiling module is also used for loading the environment unit into the file management example and constructing a compiling task example through the file management example; performing compilation on the task instance to determine a compilation result.

In one possible design, before loading the environment unit into the file management instance, the compiling module further includes:

the compiling module is also used for creating an interface unit loader according to the context module of the current thread; constructing a source file example according to the compiling unit name of the interface original file; adding the source file instance to the file management instance using the interface unit loader;

correspondingly, the compiling module is also used for loading the environment unit into the file management instance, and comprises the following steps:

and the compiling module is also used for loading the environment unit into the file management instance by using the interface unit loader.

In one possible design, the encapsulating module is configured to determine the target data stream interface according to the compiling result by using an interface encapsulator, and includes:

an encapsulation module for determining a request-to-process mapper based on an application context module of the interface encapsulator;

the packaging module is also used for determining each corresponding interface method unit according to the compiling result;

the encapsulation module is also used for screening out a target method unit with annotation as a request mapper from each interface method unit according to the request-processing mapper;

and the packaging module is also used for registering a target data stream interface by utilizing the dynamic proxy module according to the compiling result and the target method unit.

Optionally, after determining each corresponding interface method unit according to the compiling result, the encapsulating module further includes:

and the encapsulation module is also used for setting the private attribute of the interface method unit as the visible attribute.

In one possible design, the data stream interface dynamic orchestration device further includes:

and the sending module is used for returning the target data stream interface to the front-end system.

In a fourth aspect, the present application provides a dynamic arrangement apparatus for data stream interfaces, including:

the acquisition module is used for acquiring a dragging instruction of a user;

the system comprises a graphics library module, a module assembly interface, a service logic module and a module assembly interface, wherein the graphics library module is used for copying each service atom module to the module assembly interface in response to a dragging instruction, and the service atom modules are graphical modules formed by organizing service logics according to a preset format;

the acquisition module is also used for acquiring a logic assembly instruction of a user;

the assembling module is used for responding to the logic assembling instruction and assembling all the service atom modules into a target service module;

the processing module is used for determining an analysis request of a data stream interface according to the target service module and the preset interface parameters;

and the processing module is also used for sending an analysis request to the back-end service system so that the back-end service system can carry out dynamic analysis according to the analysis request and determine a target data stream interface.

In one possible design, the processing module is configured to determine an analysis request of a data stream interface according to a target service module and preset interface parameters, and includes:

the processing module is used for determining a mapping protocol string according to a target service module and a preset data protocol, and the mapping protocol string is used for representing each service atomic module and a service logic relation between the service atomic modules;

and the processing module is also used for determining an analysis request according to the mapping protocol string and the preset interface parameter.

In one possible design, the processing module is configured to determine a mapping protocol string according to the target service module and a preset data protocol, and includes:

and the processing module is used for establishing a mapping relation between each service atom module in the target service module and the corresponding service logic according to the format of a preset data protocol so as to determine a mapping protocol string.

Optionally, the preset data protocol is a JSON protocol, and the processing module is configured to establish a mapping relationship between each service atomic module in the target service module and the corresponding service logic according to a format of the preset data protocol to determine a mapping protocol string, where the mapping relationship includes:

the processing module is used for transmitting the target business module to the back-end service system; the back-end service system is mapped into a JSON text according to each service atomic module and corresponding service logic according to a JSON protocol; and determining a mapping protocol string according to the JSON text.

In a fifth aspect, the present application provides an electronic device, comprising:

a memory for storing program instructions;

and the processor is used for calling and executing the program instructions in the memory and executing any one of the possible data stream interface dynamic arrangement methods provided by the first aspect.

In a sixth aspect, the present application provides an electronic device, comprising:

a memory for storing program instructions;

and the processor is used for calling and executing the program instructions in the memory and executing any one of the possible data stream interface dynamic arrangement methods provided by the second aspect.

In a seventh aspect, the present application provides a storage medium, where a computer program is stored in the storage medium, where the computer program is configured to execute any one of the possible data stream interface dynamic arrangement methods provided in the first aspect.

In an eighth aspect, the present application provides a storage medium, where a computer program is stored in the storage medium, where the computer program is configured to execute any one of the possible data stream interface dynamic arrangement methods provided in the second aspect.

In a ninth aspect, the present application further provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the computer program implements any one of the possible data stream interface dynamic arrangement methods provided in the first aspect.

In a tenth aspect, the present application further provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the computer program implements any one of the possible data stream interface dynamic arrangement methods provided in the second aspect.

Drawings

In order to more clearly illustrate the technical solutions in the present application or the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.

FIG. 1 is a schematic diagram of an interface provided herein;

FIG. 2 is a schematic diagram of a front-end graphical interface logic editing interface provided by the present application;

FIG. 3 is a flowchart illustrating a method for dynamically arranging data stream interfaces according to the present disclosure;

FIG. 4 is a schematic flow chart of another dynamic data stream interface layout method provided in the present application;

FIG. 5 is a schematic structural diagram of a dynamic data stream interface editing apparatus provided in the present application;

FIG. 6 is a schematic structural diagram of a dynamic data stream interface editing apparatus provided in the present application;

fig. 7 is a schematic structural diagram of an electronic device provided in the present application;

fig. 8 is a schematic structural diagram of an electronic device provided in the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments. All other embodiments, including but not limited to combinations of embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any inventive step are within the scope of the present application.

The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

The existing API interface development is completed by directly compiling program codes bearing interface logics, namely a code customization development mode, depending on the requirements and self understanding of developers in a requirement book. However, this method makes developers unable to decouple the implementation logic of the interface from the code grammar specification, the developers are burnt out by various repeated codes, the development efficiency of the interface is low, and the interfaces with the same logic function cannot be directly used in different platform environments, and the development of the repeated interfaces in different platform environments is needed, which results in a great waste of manpower and material resources.

The above problems are not solved, and the inventive concept of the present application is directed to:

the interface core logic is constructed by utilizing a graphical front-end system, and then the code program package corresponding to the interface is automatically and dynamically arranged by utilizing a back-end service system according to the interface core logic. The user directly assembles interface logic in the front-end system through a graphical interface, and then the back-end system automatically compiles and packages the interface logic into a required target data stream interface according to the application environment.

For ease of understanding, the terms referred to in this application are described below.

The interfaces are channels for data interaction between users and systems, between modules and between front-end systems and back-end systems, and the interaction parties complete the receiving and sending of external data through the interfaces. For example, the interface receives a request sent by the system at one end of the interface, converts the request into a request mode which can be identified by the system at the other end, and processes the request to the system at the other end.

Fig. 1 is a schematic diagram of an interface provided in the present application. As shown in fig. 1, a front-end system 11 needs to pass data or requests to a back-end system 12. For different data or requests, either the same back-end system corresponds to different front-end systems, or the same front-end system corresponds to a plurality of back-end systems, each needs a corresponding data transmission channel, i.e., the interface 13, to transmit data, so as to form a data stream.

The following describes the method for dynamically arranging pages by using a data stream interface according to the present application in detail with reference to the accompanying drawings.

Fig. 2 is a schematic diagram of a front-end graphical interface logic editing interface provided in the present application. As shown in fig. 2, the graphical interface logic editing interface includes a graphical module library 21, a module assembly interface 22, a preset interface parameter filling area 23, control command buttons (such as an operation button, a basic module library button, a reset button, etc.), and an output result display area. At least one business atom module 211 customized according to business logic by a user is included in the graphic module library 21. The user drags and copies each service atomic module to be used to the module assembling interface 22, and then assembles and splices through the basic modules in the basic module library, wherein the basic modules include: logic module, Loops module, Math matching module, Text module, Lists collection module, Color module, Variables variable module, Functions function module, etc. The Logic module comprises various Logic operation modules, such as four arithmetic operations, summation operation, differentiation/integration operation and the like.

The following describes in detail how a user can automatically generate a target data stream interface by using the dynamic data stream interface layout method provided in the present application according to the interface shown in fig. 2.

Fig. 3 is a schematic flowchart of a dynamic arrangement method of a data stream interface according to the present application. As shown in fig. 3, the specific steps of the dynamic data stream interface editing method include:

s301, in response to a drag instruction of a user, copying each service atom module from the graphical module library to a module assembly interface.

In this step, the service atom module is a graphical module that organizes the service logic according to a preset format.

Specifically, a user, i.e., a developer, first needs to customize a service atomic module according to a service related to a target data stream interface. The developer disassembles the service according to the service implementation logic to obtain the minimum service unit capable of implementing the basic logic, namely the atomic service, and then the developer graphically encapsulates the atomic service according to a graphical module custom interface provided by the front-end system to form a service atomic module. Because the atomic service has higher universality and can be called by various complex services, the customized service atomic module contained in the graphical module library is more and more abundant along with the continuous perfection of developers. And developers can add the assembled complex modules into the graphical module library to form new service atom modules, namely, the nested multiplexing of the service atom modules is realized.

When a developer needs to develop a new interface, namely a target data stream interface, a business atomic module is dragged or copied from the graphical module library to the module assembly interface.

S302, responding to a logic assembly instruction of a user, and assembling all the service atom modules into a target service module.

In this step, the user uses the combination of the service atom module and the basic module to realize the service logic of the target data stream interface, and the multi-module assembly set formed by the combination is the target service module.

For example: as shown in FIG. 2, the target business module 221 in the module assembly interface 22 is obtained by splicing the business atom modules 1-3, the Variables variable modules (setting identification and setting inventory identification), the Logic module (summation), and the Lists collection module (creation collection).

S303, determining an analysis request of the data stream interface according to the target service module and the preset interface parameter.

In this step, the user, i.e. the developer, uses some basic parameters of the target data stream interface, i.e. preset interface parameters, such as: the name, type, application environment, calling method and path, input parameters, output parameters, statement and other contents are input into the preset interface parameter filling area, and after the operation button is clicked, the front-end system generates an analysis request together with the object and service logic related to the target service module 221 and the preset interface parameters.

In a possible embodiment, the step specifically includes:

S304, sending an analysis request to the back-end service system.

It should be noted that steps S301 to S304 are all completed in the front-end system. Optionally, a management system corresponding to the graphical management interface shown in fig. 2 in the front-end system may be built by using a Blockly graphical solution.

S305, receiving an analysis request sent by a front-end system, and determining an interface original file according to the analysis request and a preset dynamic template.

In this step, the back-end service system receives an analysis request sent by the front-end system, and then determines a mapping protocol string and a preset interface parameter according to the analysis request; then, resolving the mapping protocol string according to the preset interface parameters and the preset data protocol to determine each interface unit; and then, pre-reading a preset dynamic template, and adding an interface method unit in the preset dynamic template into an interface unit to determine an interface original file. The method unit comprises the following steps: interface request mode, access path specification and method declaration.

Specifically, interface units corresponding to the service atomic modules and interface method units corresponding to the service logical relations among the service atomic modules are created according to the analysis request. And then, a preset dynamic template is utilized to realize a realization method and a realization path of data request and/or processing corresponding to the business logic relationship in the application environment of the target data stream interface.

It should be noted that, in this embodiment, an implementation manner of the interface unit is a JAVA class object, and an implementation manner of the interface method unit is a JAVA method/function class, or a function object or called a function. It will of course be appreciated that the essence of a method class is also a JAVA class.

And S306, dynamically compiling the interface original file according to the application environment indicated in the analysis request.

In this step, the application environment is a platform environment used by the target data stream interface, for example, the target data stream interface is an interactive data transmission interface between a front end system of a Web page and a back end system, the front end system of the Web page may be developed based on a JavaScript protocol framework, and the back end system may be a content management system including cms (content management system) and an SQL (Structured Query Language) database. The back-end system can be generally developed based on a JAVA language platform and an SQL language, and the application environment is determined by the target data stream interface.

It should be noted that the target data stream is used for data interaction between the front-end system and the back-end service system.

In this embodiment, the step specifically includes:

determining a corresponding compiler according to the application environment;

It should be noted that the interface method unit is an interface method class, and is used for implementing an access request method or function that needs to be executed by the interface class instance object.

And S307, determining a target data stream interface according to the compiling result by using an interface wrapper.

In this step, the interface wrapper is used to decompile the compilation result file, so that the target data stream interface can be identified by the front-end graphical system, or packaged into a general language protocol structure, such as a Spring framework, so that the target data stream interface can be efficiently multiplexed.

And S308, returning a target data stream interface to the front-end system.

In this step, the back-end service system returns the automatically generated target data stream interface to the graphical management interface of the front end, so that the user can check whether the target business module established by the user has a logic error.

The embodiment provides a dynamic arrangement method of a data stream interface, which comprises the steps of responding to a dragging instruction at the front end, copying each service atom module from a graphical module library to a module assembly interface, responding to a logic assembly instruction, assembling each service atom module into a target service module, determining an analysis request of the data stream interface according to the target service module and preset interface parameters, and sending the analysis request to the rear end; and determining an interface original file at the back end according to the received analysis request and a preset dynamic template, then dynamically compiling the interface original file according to the application environment of the interface, packaging the compiling result by using an interface packaging device, and determining a target data stream interface. The method realizes that interface core logic is constructed by utilizing a graphical front-end system, and then the interface code package is automatically and dynamically arranged by utilizing a back-end service system, so as to solve the technical problem of low development efficiency caused by developing the interface by relying on direct code customization in the prior art.

Fig. 4 is a schematic flowchart of another dynamic data stream interface layout method provided in the present application. As shown in fig. 4, the method for dynamically arranging the data stream interface includes the following specific steps:

s401, in response to a drag instruction of a user, copying each service atom module from the graphical module library to a module assembly interface.

In this embodiment, a data stream interface dynamic arrangement method according to an embodiment of the present application is described by taking a target data stream interface for calculating a safety stock as an example. In the calculation of safety stock business, three business atom modules are needed, namely a stock atom module, an available stock atom module and an in-transit stock atom module. And the user copies or drags and copies the three services from the graphical module library to the module assembly interface.

S402, responding to a logic assembly instruction of a user, and assembling all the service atom modules into a target service module.

In this step, the user performs service assembly on the module assembly interface by using the basic module and the three service submodules according to the service logic of the safety stock service, so as to obtain a target service module, namely the safety stock module, and a logic relation is formed in the graphical management system.

And S403, determining a mapping protocol string according to the target service module and a preset data protocol.

In this step, the mapping protocol string is used to represent each service atomic module and the service logical relationship between each service atomic modules.

In a possible implementation manner, a mapping relationship is established between each service atomic module in the target service module and the corresponding service logic according to a format of a preset data protocol, so as to determine a mapping protocol string.

Specifically, in this embodiment, the preset data protocol is a JSON (JavaScript Object Notation) protocol, and this step specifically includes:

transmitting the target business module to a back-end service system;

and determining a mapping protocol string according to the JSON text.

For example, in the above security inventory module, the front-end system sends the security inventory module to the back-end service system, the JSON generation tool of the back-end service system maps the security inventory module into JSON texts according to the JSON protocol, and then the corresponding JSON texts are arranged according to a certain series to form a mapping protocol string.

S404, determining an analysis request according to the mapping protocol string and the preset interface parameter.

In this embodiment, after the user inputs the API interface basic information parameter of the target data stream interface corresponding to the target service module, which is the security inventory module, in the preset interface parameter filling area 23 shown in fig. 2, and clicks the operation button, the front-end system generates an analysis request together with the mapping protocol string obtained in S403 and the API interface basic information parameter.

S405, sending an analysis request to the back-end service system.

In this step, the front-end system sends the analysis request generated in the previous step to the back-end service system. It should be noted that the platform environment, i.e., the application environment, of the application required by the target data stream interface is included in the parsing request.

S406, receiving an analysis request sent by the front-end system, and determining a mapping protocol string and a preset interface parameter according to the analysis request.

In this embodiment, the back-end service system receives the parsing request, and then reads the mapping protocol string and the preset interface parameter in the parsing request, that is, the PI interface basic information parameter.

S407, resolving the mapping protocol string according to the preset interface parameters and the preset data to determine each interface unit.

In this embodiment, the interface unit is an interface JAVA class. Firstly, resolving a JSON text in a mapping protocol string by using a resolving tool according to a JSON protocol to determine to establish a blank interface JAVA class file, and then adjusting the name of the interface JAVA class according to an API convention specification corresponding to an application environment to make the name of the interface JAVA class consistent with the class name in preset interface parameters.

S408, pre-reading the preset dynamic template, and adding the interface method unit in the preset dynamic template into the interface unit to determine the interface original file.

In this step, the interface method unit includes: interface request mode, access path specification and method declaration. The preset dynamic templates can be multiple and respectively correspond to multiple request method modes and/or access path specifications.

Specifically, a preset dynamic template is read in advance to form a file stream, corresponding content in the file stream is replaced according to preset interface parameters, namely API (application program interface) basic information parameters, and corresponding interface method JAVA classes, namely interface method units, in the preset dynamic template are added to a blank interface JAVA class file established in the last step. Thus, a complete JAVA class file, i.e. an interface original file, is formed.

S409, dynamically compiling the interface original file by using a compiler, and loading an environment unit related to the application environment to the interface original file to determine a compiling result.

In this embodiment, the step specifically includes:

determining a corresponding compiler according to the application environment indicated in the analysis request, and determining a file management instance according to the compiler;

performing compilation on the task instance to determine a compilation result.

It should be noted that, in this embodiment, the compilation result is a file in class format in the JAVA framework, and the environment unit is an example of a relevant class in the JAVA compilation environment.

For example, in the above example, the calculation of the safety stock needs to be performed on the basis of stock, available stock and in-transit stock, that is, safety stock is stock-available stock-in-transit stock, when the safety stock service code is generated, the stock atomic component, the available stock atomic component and the in-transit stock atomic component, that is, the stock atomic module, the available stock atomic module and the in-transit stock atomic module, need to be converted into original codes of Java, and form new codes according to the logical relationship returned from the front end, that is, the logical relationship of each business atomic module in the analysis request (stock-available stock-in-transit stock), construct a new method (interface method unit) and corresponding return value, form method contents (specific contents of the interface method unit) in the original file (interface original file), and the original file is inherited to SimpleJavaFileObject to construct an original file instance; a standard file manager instance is constructed by realizing a specified compiling diagnosis collector (compiler) of the diagnostic Listener, a custom class loader is realized by bearing a ClassLoader, and the original file instance is injected into the custom class loader to finish dynamic compiling.

And S410, determining a target data stream interface according to a compiling result by using an interface wrapper.

In this embodiment, the method specifically includes:

determining a request-processing mapper according to an application context module of the interface wrapper, for example, using a Spring architecture protocol as a specific implementation manner of the interface wrapper, where the application context module is a Spring application context, and the request-processing mapper corresponds to requestmappinghandler mapping in a Spring framework;

determining each corresponding interface method unit, namely an interface method class according to the compiling result;

setting the private attribute of the interface method unit as a visible attribute, wherein the purpose of the step is to enable the subsequent interface method class to be called and set;

screening out a target method unit annotated as a request mapper from various interface method units according to the request-processing mapper, wherein one implementation mode of the request mapper is RequestMapping in a Spring framework;

For example, according to the ApplicationContext, all methods, i.e., interface method classes, of requestmappinghandler mapping in the context environment are obtained, attributes of the methods are set to be visible, a target method unit, which is a method capable of providing services to the outside in a target file, i.e., a compiling result, is judged, and dynamic proxy and registration are performed, so that the application environment corresponding to a container environment, i.e., a target data stream interface, can identify the existence of a new service interface, i.e., a target data stream interface.

And S411, returning a target data stream interface to the front-end system.

Fig. 5 is a schematic structural diagram of a dynamic data stream interface editing apparatus provided in the present application. The data stream interface dynamic orchestration device 500 may be implemented in software, hardware, or a combination of both.

As shown in fig. 5, the data stream interface dynamic orchestration device 500 includes:

a receiving module 501, configured to receive an analysis request sent by a front-end system;

a request processing module 502, configured to determine an interface source file according to the parsing request and a preset dynamic template;

a compiling module 503, configured to dynamically compile the interface raw file according to an application environment indicated in the analysis request to determine a compiling result, where the application environment is a platform environment used by a target data stream interface, and the target data stream is used for data interaction between the front-end system and the back-end service system;

and an encapsulation module 504, configured to determine the target data stream interface according to the compiling result by using an interface encapsulator.

In a possible design, the request processing module 502 is configured to determine an interface source file according to the parsing request and a preset dynamic template, and includes:

a request processing module 502, configured to determine a mapping protocol string and a preset interface parameter according to the parsing request;

the request processing module 502 is further configured to parse the mapping protocol string according to the preset interface parameter and the preset data protocol to determine each interface unit;

the request processing module 502 is further configured to pre-read a preset dynamic template, and add an interface method unit in the preset dynamic template to the interface unit to determine an interface original file, where the method unit includes: interface request mode, access path specification and method declaration.

In a possible design, the compiling module 503 is configured to dynamically compile the interface raw file according to the application environment indicated in the parsing request to determine a compiling result, and includes:

a compiling module 503, configured to determine a corresponding compiler according to the application environment;

the compiling module 503 is further configured to dynamically compile the interface raw file by using a compiler, and load an environment unit related to the application environment to the interface raw file to determine a compiling result.

In a possible design, the compiling module 503 is further configured to dynamically compile an interface raw file by using a compiler, and load an environment unit related to an application environment to the interface raw file to determine a compiling result, including:

the compiling module 503 is further configured to determine a file management instance according to the compiler;

the compiling module 503 is further configured to load the environment unit into the file management instance, and construct a compiling task instance through the file management instance; performing compilation on the task instance to determine a compilation result.

In a possible design, before the compiling module 503 is further configured to load the environment unit into the file management instance, the compiling module further includes:

the compiling module 503 is further configured to create an interface unit loader according to the context module of the current thread; constructing a source file example according to the compiling unit name of the interface original file; adding the source file instance to the file management instance using the interface unit loader;

correspondingly, the compiling module 503 is also used for loading the environment unit into the file management instance, and includes:

the compiling module 503 is further configured to load the environment unit into the file management instance by using the interface unit loader.

In one possible design, the encapsulating module 504 is configured to determine the target data stream interface according to the compiling result by using an interface encapsulator, and includes:

an encapsulation module 504 for determining a request-to-process mapper from an application context module of the interface encapsulator;

the packaging module 504 is further configured to determine corresponding interface method units according to the compiling result;

the encapsulation module 504 is further configured to screen out a target method unit annotated as a request mapper from the interface method units according to the request-to-process mapper;

the encapsulation module 504 is further configured to register the target data stream interface with the dynamic proxy module according to the compilation result and the target method unit.

Optionally, the encapsulating module 504 is further configured to, after determining each corresponding interface method unit according to the compiling result, further include:

the encapsulation module 504 is further configured to set the private attribute of the interface method unit as a visible attribute.

It should be noted that the dynamic data stream interface arranging device provided in the embodiment shown in fig. 5 may execute the method corresponding to the back-end service system provided in any one of the above method embodiments, and the specific implementation principle, technical features, term explanation and technical effects thereof are similar and will not be described herein again.

Fig. 6 is a schematic structural diagram of a dynamic data stream interface editing apparatus provided in the present application. The data stream interface dynamic orchestration device 600 may be implemented in software, hardware, or a combination of both.

As shown in fig. 6, the data stream interface dynamic orchestration device 600 includes:

an obtaining module 601, configured to obtain a dragging instruction of a user;

the graphic library module 602 is configured to copy, in response to a drag instruction, each service atom module to a module assembly interface, where the service atom module is a graphic module formed by organizing service logic according to a preset format;

the obtaining module 601 is further configured to obtain a logic assembly instruction of a user;

an assembling module 603, configured to, in response to the logic assembling instruction, assemble each service atom module into a target service module;

a processing module 604, configured to determine an analysis request of a data stream interface according to the target service module and a preset interface parameter;

the processing module 604 is further configured to send an analysis request to the back-end service system, so that the back-end service system performs dynamic analysis according to the analysis request, and determines a target data stream interface.

In a possible design, the processing module 604 is configured to determine a parsing request of a data stream interface according to a target service module and preset interface parameters, and includes:

a processing module 604, configured to determine a mapping protocol string according to a target service module and a preset data protocol, where the mapping protocol string is used to represent each service atomic module and a service logical relationship between the service atomic modules;

the processing module 604 is further configured to determine a parsing request according to the mapping protocol string and the preset interface parameter.

In one possible design, the processing module 604 is configured to determine a mapping protocol string according to a target service module and a preset data protocol, and includes:

the processing module 604 is configured to establish a mapping relationship between each service atomic module in the target service module and the corresponding service logic according to a format of a preset data protocol, so as to determine a mapping protocol string.

Optionally, the preset data protocol is a JSON protocol, and the processing module 604 is configured to establish a mapping relationship between each service atomic module in the target service module and the corresponding service logic according to a format of the preset data protocol to determine a mapping protocol string, where the mapping relationship includes:

a processing module 604, configured to transmit the target service module to a backend service system; the back-end service system is mapped into a JSON text according to each service atomic module and corresponding service logic according to a JSON protocol; and determining a mapping protocol string according to the JSON text.

It should be noted that the dynamic data stream interface layout device provided in the embodiment shown in fig. 6 may execute the method corresponding to the front-end system provided in any of the above method embodiments, and the specific implementation principle, technical features, term interpretation, and technical effects thereof are similar and will not be described herein again.

Fig. 7 is a schematic structural diagram of an electronic device provided in the present application. As shown in fig. 7, the electronic device 700 is applied to a backend service system, and may include: at least one processor 701 and a memory 702. Fig. 7 shows an electronic device as an example of a processor.

And a memory 702 for storing programs. In particular, the program may include program code including computer operating instructions.

The memory 702 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.

The processor 701 is configured to execute computer-executable instructions stored by the memory 702 to implement the methods described in the method embodiments above.

The processor 701 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.

Alternatively, the memory 702 may be separate or integrated with the processor 701. When the memory 702 is a device independent from the processor 701, the electronic device 700 may further include:

a bus 703 for connecting the processor 701 and the memory 702. The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. Buses may be classified as address buses, data buses, control buses, etc., but do not represent only one bus or type of bus.

Alternatively, in a specific implementation, if the memory 702 and the processor 701 are implemented in a single chip, the memory 702 and the processor 701 may communicate via an internal interface.

Fig. 8 is a schematic structural diagram of an electronic device provided in the present application. As shown in fig. 8, the electronic device 800 application and front-end system may include: at least one processor 801 and a memory 802. Fig. 8 shows an electronic device as an example of a processor.

The memory 802 stores programs. In particular, the program may include program code including computer operating instructions.

Memory 802 may comprise high-speed RAM memory and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.

The processor 801 is configured to execute computer-executable instructions stored in the memory 802 to implement the methods described in the method embodiments above.

The processor 801 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.

Alternatively, the memory 802 may be separate or integrated with the processor 801. When the memory 802 is a device independent of the processor 801, the electronic device 800 may further include:

a bus 803 for connecting the processor 801 and the memory 802. The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. Buses may be classified as address buses, data buses, control buses, etc., but do not represent only one bus or type of bus.

Alternatively, in a specific implementation, if the memory 802 and the processor 801 are integrated into a chip, the memory 802 and the processor 801 may communicate through an internal interface.

The present application also provides a computer-readable storage medium, which may include: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, are specifically, the computer-readable storage medium stores program instructions, and the program instructions are used in the method corresponding to the backend service system in the foregoing method embodiments.

The present application also provides a computer-readable storage medium, which may include: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, are specifically, the computer-readable storage medium stores program instructions, and the program instructions are used in the method corresponding to the front-end system in the above method embodiments.

The present application further provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the computer program implements the method corresponding to the backend service system in the foregoing method embodiments.

The present application further provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the computer program implements the method corresponding to the front-end system in the foregoing method embodiments.

Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A dynamic arranging method for data stream interface is applied to a back-end service system, and comprises the following steps:

receiving an analysis request sent by a front-end system;

dynamically compiling the interface original file according to an application environment indicated in the analysis request to determine a compiling result, wherein the application environment is a platform environment used by a target data stream interface, and the target data stream is used for data interaction between the front-end system and the back-end service system;

and determining the target data stream interface according to the compiling result by using an interface wrapper.

2. The method for dynamically arranging data stream interfaces according to claim 1, wherein the determining the original interface file according to the parsing request and a preset dynamic template includes:

analyzing the mapping protocol string according to the preset interface parameters and a preset data protocol to determine each interface unit;

pre-reading a preset dynamic template, and adding an interface method unit in the preset dynamic template into the interface unit to determine the interface original file, wherein the method unit comprises the following steps: interface request mode, access path specification and method declaration.

3. The method for dynamically arranging data stream interfaces according to claim 1, wherein the dynamically compiling the interface raw file according to the application environment indicated in the parsing request to determine the compilation result includes:

determining a corresponding compiler according to the application environment;

and dynamically compiling the interface original file by using a compiler, and loading an environment unit related to the application environment to the interface original file to determine the compiling result.

4. The method for dynamically arranging data stream interfaces according to claim 3, wherein the dynamically compiling the interface raw file by using a compiler and loading the environment units related to the application environment to the interface raw file to determine the compiling result comprises:

determining a file management instance according to the compiler;

loading the environment unit into the file management instance, and constructing a compiling task instance through the file management instance;

performing compilation on the task instance to determine the compilation result.

5. The method of claim 4, wherein prior to said loading said environment unit into said file management instance, further comprising:

constructing a source file instance according to the compiling unit name of the interface original file;

adding, with the interface unit loader, the source file instance to the file management instance;

correspondingly, the loading the environment unit into the file management instance includes:

loading the environment unit into the file management instance with the interface unit loader.

6. The method for dynamically arranging data stream interfaces according to claim 1, wherein the determining the target data stream interface according to the compiling result by using an interface wrapper comprises:

determining a request-to-process mapper based on an application context module of the interface wrapper;

determining each corresponding interface method unit according to the compiling result;

and registering the target data stream interface by using a dynamic proxy module according to the compiling result and the target method unit.

7. The method according to claim 6, further comprising, after determining each corresponding interface method unit according to the compiling result, the following steps:

and setting the private attribute of the interface method unit as a visible attribute.

8. The method for dynamically arranging a data stream interface according to claim 1, further comprising:

and returning the target data stream interface to the front-end system.

9. A dynamic arranging method for a data stream interface is applied to a front-end system and comprises the following steps:

responding to a logic assembly instruction of a user, and assembling each service atomic module into a target service module;

determining an analysis request of a data stream interface according to the target service module and preset interface parameters;

and sending the analysis request to a back-end service system so that the back-end service system performs dynamic analysis according to the analysis request and determines a target data stream interface.

10. The method for dynamically arranging data stream interfaces according to claim 9, wherein the determining the parsing request of a data stream interface according to the target service module and preset interface parameters includes:

and determining the analysis request according to the mapping protocol string and preset interface parameters.

11. The method for dynamically arranging data stream interfaces according to claim 10, wherein the determining a mapping protocol string according to the target service module and a preset data protocol includes:

and establishing a mapping relation between each service atom module in the target service module and the corresponding service logic according to a format of a preset data protocol so as to determine the mapping protocol string.

12. The method according to claim 11, wherein the preset data protocol is a JSON protocol, and the establishing a mapping relationship between each service atom module in the target service module and the corresponding service logic according to a format of the preset data protocol to determine the mapping protocol string includes:

transmitting the target business module to a back-end service system;

the back-end service system is mapped into a JSON text according to each business atom module and corresponding business logic according to a JSON protocol;

and determining the mapping protocol string according to the JSON text.

13. A data stream interface dynamic orchestration device, comprising:

the compiling module is used for dynamically compiling the interface original file according to the application environment indicated in the analysis request so as to determine a compiling result, wherein the application environment is a platform environment used by a target data stream interface, and the target data stream is used for data interaction between the front-end system and a back-end service system;

14. A data stream interface dynamic orchestration device, comprising:

the acquisition module is used for acquiring a dragging instruction of a user;

the graphical library module is used for responding to the dragging instruction and copying each service atom module to a module assembly interface, and the service atom module is a graphical module formed by organizing service logic according to a preset format;

the obtaining module is further configured to obtain a logic assembly instruction of the user;

the assembling module is used for responding to the logic assembling instruction and assembling each service atom module into a target service module;

the processing module is used for determining an analysis request of a data stream interface according to the target service module and preset API interface parameters; and sending the analysis request to a back-end service system so that the back-end service system performs dynamic analysis according to the analysis request and determines a target data stream interface.

15. An electronic device, comprising:

a processor; and the number of the first and second groups,

a memory for storing a computer program for the processor;

wherein the processor is configured to perform the method of dynamic orchestration of data flow interfaces of any of claims 1-8 via execution of the computer program.

16. An electronic device, comprising:

a processor; and the number of the first and second groups,

a memory for storing a computer program for the processor;

wherein the processor is configured to perform the method of dynamic orchestration of data flow interfaces of any of claims 9 to 12 via execution of the computer program.

17. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the method for dynamic orchestration of data flow interfaces according to any one of claims 1 to 8.

18. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the method for dynamic orchestration of data flow interfaces according to any one of claims 9 to 12.

19. A computer program product comprising a computer program, characterized in that the computer program realizes the method of any of claims 1 to 8 when executed by a processor.

20. A computer program product comprising a computer program, characterized in that the computer program realizes the method of any of claims 9 to 12 when executed by a processor.