CN114217790A

CN114217790A - Interface scheduling method and device, electronic equipment and medium

Info

Publication number: CN114217790A
Application number: CN202111622083.4A
Authority: CN
Inventors: 杨舸
Original assignee: Shenzhen Lexin Software Technology Co Ltd
Current assignee: Shenzhen Lexin Software Technology Co Ltd
Priority date: 2021-12-28
Filing date: 2021-12-28
Publication date: 2022-03-22

Abstract

The embodiment of the application discloses an interface scheduling method, an interface scheduling device, electronic equipment and a medium. The method comprises the following steps: acquiring interface requirement information; determining at least two associated target logic blocks according to the interface requirement information; and arranging the at least two target logic blocks, and storing the arranged target logic blocks in a database, so that the associated target logic blocks are scheduled from the database according to the arranged execution logic when an interface scheduling request is received. In the technical scheme, the functional code blocks corresponding to the existing standard interfaces are freely arranged according to the requirements of the client interfaces so as to adapt the interfaces required by the clients, thereby avoiding the limitation of developing different adaptive interfaces according to the interface standards of different clients, reducing the asset access cost and the development cost of the functional code blocks, and improving the interface docking efficiency.

Description

Interface scheduling method and device, electronic equipment and medium

Technical Field

The embodiment of the application relates to the field of software development, in particular to an interface scheduling method, an interface scheduling device, electronic equipment and a medium.

Background

In the financial asset access business, the different business company provides services such as credit granting, body checking, transaction, repayment, account checking, credit clearing and the like for a user by providing a financial technology company interface for the user with the loan demand. In the process, the data acquisition is realized between the different industry company and the financial technology company through the interface docking of the two parties.

Because each different industry company has a set of interface standards, when the finance and technology company interfaces with each different industry company, different adaptive interfaces need to be developed according to the interface standards of different companies. This approach has the disadvantage of longer development cycles and higher maintenance costs, thereby increasing the cost of interfacing with the customer.

Disclosure of Invention

The embodiment of the application provides an interface arranging and scheduling method, an interface arranging and scheduling device, electronic equipment and a medium.

In an embodiment, an embodiment of the present application provides an interface scheduling method, where the method includes:

acquiring interface requirement information;

determining at least two associated target logic blocks according to the interface requirement information;

and arranging the at least two target logic blocks, and storing the arranged target logic blocks in a database, so that the associated target logic blocks are scheduled from the database according to the arranged execution logic when an interface scheduling request is received.

In one embodiment, an interface scheduling apparatus is provided in an embodiment of the present application, and the apparatus includes:

the interface information acquisition module is used for acquiring interface requirement information;

the logic block determining module is used for determining at least two associated target logic blocks according to the interface requirement information;

and the logic block arranging module is used for arranging the at least two target logic blocks and storing the arranged target logic blocks in the database so as to schedule the associated target logic blocks from the database according to the arranged execution logic when receiving the interface scheduling request.

In one embodiment, an embodiment of the present application provides an electronic device, where the electronic device includes:

one or more processors;

a memory for storing one or more programs;

when the one or more programs are executed by the one or more processors, the one or more processors implement the interface orchestration scheduling method according to any of the embodiments of the application.

In one embodiment, the present application provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the interface orchestration scheduling method according to any one of the embodiments of the present application.

Drawings

FIG. 1 is a flowchart of an interface scheduling method according to an embodiment of the present application;

FIG. 2 is a block diagram of a logic block reservation provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of a logic block arrangement provided by an embodiment of the present application;

FIG. 4 is a flowchart of an interface scheduling method according to another embodiment of the present application;

FIG. 5 is a flow chart of interface scheduling provided by another embodiment of the present application;

FIG. 6 is a block diagram of an interface scheduling system according to another embodiment of the present application;

FIG. 7 is a block diagram of an interface scheduling apparatus according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

The present application is described in further detail below with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting of the application. It should be further noted that, for the convenience of description, only some of the structures related to the present application are shown in the drawings, not all of the structures.

Fig. 1 is a flowchart of an interface scheduling method according to an embodiment of the present application, where the embodiment is applicable to a scenario of interface adaptation. The method can be executed by the interface scheduling apparatus provided in the embodiments of the present application, and the apparatus can be implemented by software and/or hardware, and can be integrated in an electronic device.

As shown in fig. 1, the interface scheduling method provided in the embodiment of the present application may include the following steps:

and S110, acquiring interface requirement information.

The interface requirement information may be an interface document of the client, and the content of the interface document may include an interface name and a description of a function to be implemented by the interface. The method for acquiring the interface requirement information is not limited in the embodiment of the application.

And S120, determining at least two associated target logic blocks according to the interface requirement information.

The target logic block is screened from the function code block corresponding to the existing standardized interface with the minimum fine granularity. In the embodiment of the application, after the interface requirement information is obtained, a function code block adapted to the interface requirement is found from a function code block corresponding to the existing standardized interface with the smallest fine granularity and is used as a target logic block. The number of target logic blocks can be set according to actual requirements.

In this embodiment of the application, optionally, the determining, according to the interface requirement information, at least two associated target logic blocks includes:

determining function information required to be realized by the interface according to the interface requirement information;

and determining at least two associated target logic blocks according to the function information.

Wherein the function information is a description of the function implemented by the interface.

Illustratively, in a specific scenario, the acquired interface requirement information is a credit granting application interface, and the function information to be implemented by the interface includes third party registration account, collection and storage of third party information, and credit granting for the third party. After the interface requirement information is acquired, according to the functions to be realized by the interface, the third-party user registration logic block, the storage ocr information logic block, the storage face-brushing information logic block and the initiation special credit granting logic block can be provided to the provider of the interface requirement information as target logic blocks. The third-party user registration logic block is used for providing an account registration function, for example, receiving information such as a mobile phone number or an identity card number input by a third-party user, and registering an account for the third-party user according to the input information; the storage ocr information logic block and the storage face brushing information logic block are respectively used for receiving and storing ocr information and face image information of a third-party user so as to check the information later and judge whether the third-party user meets credit granting conditions; the special trust initiating logic block is used for initiating trust and returning a trust result to the third-party user.

In the embodiment of the application, the function information required to be realized by the interface is acquired from the interface requirement information, so that the adaptive target logic block can be found more quickly and accurately, and the requirements of customers are met.

In this embodiment of the application, optionally, before the obtaining of the interface requirement information, the method includes:

storing a function code block corresponding to the existing standardized interface as a candidate logic block in a database;

accordingly, the method can be used for solving the problems that,

determining at least two associated target logic blocks according to the interface requirement information, including:

and acquiring at least two associated target logic blocks from the candidate logic blocks according to the interface requirement information.

The candidate logic block is a function code block corresponding to the existing standardized interface with the minimum fine granularity. In the embodiment of the application, all candidate logic blocks can be stored in the database in advance, and after the interface requirement information is obtained, the target logic block associated with the interface requirement information can be directly inquired and scheduled from the database.

Fig. 2 is a schematic diagram of a logic block reservation provided by an embodiment of the present application. As shown in fig. 2, fig. 2 illustrates an interface of the credit granting business system, where the numbers, names, and functional descriptions of existing multiple logic blocks are illustrated in the interface. After the interface requirement information is acquired, a proper logic block can be selected from a plurality of logic blocks displayed in the interface, and operations such as editing, parameter configuration and exporting are performed on the selected logic block.

In the embodiment of the application, the existing standardized interface with the smallest fine granularity is abstracted into the logic block and is stored in the database as the candidate logic block, so that support is provided for the subsequent acquisition and arrangement of the target logic block.

S130, arranging the at least two target logic blocks, and storing the arranged target logic blocks in a database, so that the associated target logic blocks are scheduled from the database according to the arranged execution logic when an interface scheduling request is received.

The arranging is to configure the required target logic blocks according to the interface requirement information, and to hierarchy the target logic blocks according to the actual requirements. The hierarchy represents the execution logic, i.e., the scheduling order, of the target logical block.

According to the method and the device, the adaptive target logic blocks are found according to the interface demand information, then the target logic blocks are arranged and stored in advance, and then when an interface scheduling request initiated by a client is received, the corresponding logic blocks can be directly obtained, the logic blocks are sequentially scheduled according to a scheduling sequence, and finally, the interface parameters are returned.

FIG. 3 is a schematic diagram of a logic block arrangement according to an embodiment of the present application. As shown in fig. 3, after the interface requirement information is acquired, an interface is added or defined in the system. The interface of the new interface in fig. 3 is named as a credit granting application in the chinese, and the interface is described as user registration and credit granting. And four target logic blocks are adapted to the newly added interface according to the interface requirement information, wherein the four target logic blocks are respectively as follows: a third party user registration logic block, a saving ocr information logic block, a saving face brushing information logic block and an initiating special credit granting logic block. Wherein, the third party user registration logic block is configured in the layer 1, the saving ocr information logic block and the saving face brushing information logic block are configured in the layer 2, and the initiating special trust logic block is configured in the layer 3. And when an interface scheduling request is subsequently received, scheduling the logic blocks in each layer according to the sequence of the layer 1, the layer 2 and the layer 3, and returning interface parameters to a third-party user. The calling of the logic block in the embodiment of the application is generalized calling using a dubbo, a corresponding dubbo interface is found according to the logic block coding, and the calling of the logic block is executed.

In this embodiment of the application, optionally, the storing the organized target logic block in a database includes:

and storing the arranged target logic block in a database in a json format so as to obtain the execution logic of the target logic block according to the json format when the target logic block is scheduled.

The json is a lightweight data exchange format, adopts a text format completely independent of a programming language to store and represent data, has a simple and clear hierarchical structure, is easy to read and write by people, and is also easy to analyze and generate by a machine.

Taking the four target logic blocks and the hierarchy shown in fig. 3 as an example, the target logic blocks which are arranged in fig. 3 generate a corresponding json format, and the codes are as follows:

wherein layer # 0: layer denotes a hierarchy, 0 denotes a 0 th layer, layer #0 corresponds to the hierarchy 1 in fig. 3, and logicCode denotes the corresponding target logical block encoding.

When an interface scheduling request initiated by a client is received, json needs to be firstly analyzed into a MethodConfigCacheBean object, and then a scheduling step is executed. The purpose of this step is to convert the string into a java object.

According to the method and the device, all the arranged logic blocks are stored in a json format, the execution logic of each logic block is stored, and when an interface scheduling request is received, the logic blocks which need to be scheduled and the scheduling sequence of the logic blocks can be clearly known.

Fig. 4 is a flowchart of an interface scheduling method according to another embodiment of the present application, where the embodiment performs optimization based on the above embodiment, and the specific optimization steps are as follows:

and S210, acquiring interface requirement information.

S220, determining at least two associated target logic blocks according to the interface requirement information.

And S230, performing hierarchical distribution on the at least two target logic blocks according to a preset rule so as to sequentially schedule the target logic blocks in different layers according to the hierarchy when the interface scheduling request is received.

The preset rule comprises a preset scheduling sequence of each target logic block. Further, target logic blocks are distributed into all the layers according to preset rules, and when an interface scheduling request initiated by a client is received, the target logic blocks in different layers are sequentially scheduled from layer 1.

In this embodiment of the application, optionally, the performing hierarchical allocation on the at least two target logic blocks according to a preset rule includes:

and distributing the target logic blocks to be executed in series to different levels according to a preset rule, and distributing the target logic blocks to be executed in parallel to the same level, so that the target logic blocks in different levels are sequentially subjected to serial scheduling according to the levels when an interface scheduling request is received, and the target logic blocks in the same level are subjected to asynchronous parallel scheduling.

Taking the four logic blocks shown in fig. 3 as an example, the logic blocks in level 1, level 2 and level 3 need to be executed serially in level, while the two logic blocks of the save ocr information logic block and the save brush face information logic block in level 2 can be executed asynchronously and in parallel. When the logic block in the previous layer reports errors, the logic block in the next layer is not executed; when one logic block reports error, the execution of other logic blocks is not influenced.

And S240, storing the organized target logic block in a database so as to call the associated target logic block from the database according to the organized execution logic when the interface call request is received.

Fig. 5 is a flowchart of interface scheduling according to another embodiment of the present application. As shown in fig. 5, the flow starts from the partner calling the interface, and is executed step by step in the order of the arrows until the interface parameters are returned.

Fig. 6 is a block diagram of an interface scheduling system according to another embodiment of the present application, in which after a client initiates an interface scheduling request, the system performs an operation of parsing a schedule by scheduling a scheduling service.

Fig. 7 is a block diagram of a structure of an interface scheduling apparatus according to an embodiment of the present application, where the apparatus is capable of executing an interface scheduling method according to any embodiment of the present application, and has functional modules and beneficial effects corresponding to the execution method. As shown in fig. 7, the apparatus may include:

the interface information obtaining module 710 is configured to obtain the interface requirement information.

A logic block determining module 720, configured to determine at least two associated target logic blocks according to the interface requirement information.

The logic block arranging module 730 is configured to arrange the at least two target logic blocks, and store the arranged target logic blocks in the database, so that when an interface scheduling request is received, the associated target logic blocks are scheduled from the database according to the arranged execution logic.

In this embodiment of the application, the logic block determining module 720 is further configured to:

In this embodiment of the application, the logic block arranging module 730 includes:

and the layer distribution unit is used for performing layer distribution on the at least two target logic blocks according to a preset rule so as to sequentially schedule the target logic blocks in different layers according to the layers when the interface scheduling request is received.

In this embodiment of the application, the hierarchical allocation unit is further configured to:

In an embodiment of the present application, the apparatus further includes:

and the logic block storage module is used for storing the function code blocks corresponding to the existing standardized interfaces as candidate logic blocks in a database.

In this embodiment of the application, the logic block arranging module 730 is further configured to:

The product can execute the interface scheduling method provided by the embodiment of the application, and has corresponding functional modules and beneficial effects of the execution method.

Fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application. FIG. 8 illustrates a block diagram of an exemplary electronic device 812 suitable for use in implementing embodiments of the present application. The electronic device 812 shown in fig. 8 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.

As shown in fig. 8, electronic device 812 may include: one or more processors 816; a memory 828, configured to store one or more programs, which when executed by the one or more processors 816 cause the one or more processors 816 to implement the interface scheduling method provided in this embodiment of the present application, include:

acquiring interface requirement information;

Components of electronic device 812 may include, but are not limited to: one or more processors 816, a memory 828, and a bus 818 that couples the various device components including the memory 828 and the processors 816.

Bus 818 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, micro-channel architecture (MAC) bus, transaction ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

Electronic device 812 typically includes a variety of computer device-readable storage media. These storage media may be any available storage media that can be accessed by electronic device 812 and includes both volatile and nonvolatile storage media, removable and non-removable storage media.

Memory 828 may include computer device readable storage media in the form of volatile memory, such as Random Access Memory (RAM)830 and/or cache memory 832. The electronic device 812 may further include other removable/non-removable, volatile/nonvolatile computer device storage media. By way of example only, storage system 834 may be used to read from or write to non-removable, nonvolatile magnetic storage media (not shown in FIG. 8, often referred to as "hard drives"). Although not shown in FIG. 8, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical storage medium) may be provided. In such cases, each drive may be connected to the bus 818 by one or more data storage media interfaces. Memory 828 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the application.

A program/utility 840 having a set (at least one) of program modules 842, including but not limited to an operating device, one or more application programs, other program modules, and program data, may be stored in, for example, memory 828, each of which examples or some combination thereof may include an implementation of a network environment. Program modules 842 generally perform the functions and/or methodologies of embodiments described herein.

Electronic device 812 may also communicate with one or more external devices 814, a display 824, etc., and/or with one or more devices that enable a user to interact with electronic device 812, and/or with any devices (e.g., network cards, modems, etc.) that enable electronic device 812 to communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interfaces 822. Also, the electronic device 812 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the internet) via the network adapter 820. As shown in FIG. 8, the network adapter 820 communicates with the other modules of the electronic device 812 over the bus 818. It should be appreciated that although not shown in FIG. 8, other hardware and/or software modules may be used in conjunction with electronic device 812, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID devices, tape drives, and data backup storage devices, among others.

The processor 816 executes various functional applications and data processing by executing at least one of other programs of the plurality of programs stored in the memory 828, for example, to implement the interface scheduling method provided by the embodiment of the present application.

One embodiment of the present application provides a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to perform the interface orchestration scheduling method provided by the embodiments of the present application, including:

acquiring interface requirement information;

The computer storage media of the embodiments of the present application may take any combination of one or more computer-readable storage media. The computer readable storage medium may be a computer readable signal storage medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor device, apparatus, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In embodiments of the present application, a computer readable storage medium may be any tangible storage medium that can contain, or store a program for use by or in connection with an instruction execution apparatus, device, or apparatus.

A computer readable signal storage medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal storage medium may also be any computer readable storage medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution apparatus, device, or apparatus.

Program code embodied on a computer readable storage medium may be transmitted using any appropriate storage medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or device. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present application and the technical principles employed. It will be understood by those skilled in the art that the present application is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the application. Therefore, although the present application has been described in more detail with reference to the above embodiments, the present application is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present application, and the scope of the present application is determined by the scope of the appended claims.

Claims

1. An interface scheduling method, the method comprising:

acquiring interface requirement information;

2. The method of claim 1, wherein determining at least two associated target logic blocks according to the interface requirement information comprises:

3. The method of claim 1, wherein said programming said at least two target logical blocks comprises:

and performing hierarchical distribution on the at least two target logic blocks according to a preset rule so as to sequentially schedule the target logic blocks in different layers according to the hierarchy when an interface scheduling request is received.

4. The method according to claim 3, wherein said performing hierarchical allocation on said at least two target logical blocks according to a preset rule comprises:

5. The method of claim 1, wherein before obtaining the interface requirement information, the method comprises:

accordingly, the method can be used for solving the problems that,

6. The method of claim 1, wherein storing the orchestrated target logical block in a database comprises:

7. An interface orchestration scheduling apparatus, the apparatus comprising:

8. The method of claim 7, wherein the logical block orchestration module is further configured to:

9. An electronic device, characterized in that the electronic device comprises:

one or more processors;

a memory for storing one or more programs;

the one or more programs, when executed by the one or more processors, implement the interface orchestration scheduling method of any of claims 1-6.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the interface orchestration scheduling method according to any one of claims 1-6.