CN116483899A - Calling method and device for converged service interface, electronic equipment and storage medium - Google Patents
Calling method and device for converged service interface, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN116483899A CN116483899A CN202310371209.8A CN202310371209A CN116483899A CN 116483899 A CN116483899 A CN 116483899A CN 202310371209 A CN202310371209 A CN 202310371209A CN 116483899 A CN116483899 A CN 116483899A
- Authority
- CN
- China
- Prior art keywords
- service
- interface
- service interface
- calling
- called
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 63
- 230000004927 fusion Effects 0.000 claims abstract description 52
- 238000013507 mapping Methods 0.000 claims abstract description 40
- 238000012545 processing Methods 0.000 claims abstract description 28
- 230000000007 visual effect Effects 0.000 claims description 26
- 238000006243 chemical reaction Methods 0.000 claims description 20
- 230000002159 abnormal effect Effects 0.000 claims description 17
- 238000012544 monitoring process Methods 0.000 claims description 17
- 238000012795 verification Methods 0.000 claims description 17
- 244000035744 Hura crepitans Species 0.000 claims description 13
- 238000004590 computer program Methods 0.000 claims description 7
- 238000004806 packaging method and process Methods 0.000 claims description 5
- 230000008569 process Effects 0.000 abstract description 10
- 238000005516 engineering process Methods 0.000 abstract description 4
- 239000008186 active pharmaceutical agent Substances 0.000 description 12
- 230000006870 function Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 4
- 238000005538 encapsulation Methods 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 210000001503 joint Anatomy 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000033228 biological regulation Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000009472 formulation Methods 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/258—Data format conversion from or to a database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/52—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow
- G06F21/53—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow by executing in a restricted environment, e.g. sandbox or secure virtual machine
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention discloses a calling method and a device thereof for a converged service interface, electronic equipment and a storage medium, and relates to the technical field of cloud computing, wherein the calling method comprises the following steps: analyzing a service call request sent by a user side, and determining the number of service interfaces to be called based on the service call request, wherein the service call request carries a service identifier of a target financial service to be executed; under the condition that the number of the service interfaces to be called is larger than or equal to a preset number threshold value, inquiring a service interface mapping table by a service identifier to obtain a fusion service interface; and calling the fusion service interface to execute the target financial service. The invention solves the technical problems of complicated processing process and lower efficiency of the method for sequentially calling the single service interface to process the service in the related technology.
Description
Technical Field
The invention relates to the technical field of cloud computing, in particular to a method and a device for calling a converged service interface, electronic equipment and a storage medium.
Background
In order to avoid the problem of data island among different business systems, the current cloud computing technology and business services are developed at a high speed, and the products in the systems and the systems are required to be in butt joint.
In the related art, when a service system provides related services to be in butt joint with other components or systems, the service system is often realized through a service interface, for example, data is read through a calling interface, and the like, generally, a complete transaction is required to be completed by calling a plurality of service interfaces together.
In view of the above problems, no effective solution has been proposed at present.
Disclosure of Invention
The embodiment of the invention provides a method and a device for calling a converged service interface, electronic equipment and a storage medium, which at least solve the technical problems of complicated processing process and low efficiency of a method for sequentially calling a single service interface to process business in the related technology.
According to an aspect of the embodiment of the present invention, there is provided a method for invoking a converged service interface, including: analyzing a service call request sent by a user side, and determining the number of service interfaces to be called based on the service call request, wherein the service call request carries a service identifier of a target financial service to be executed; and under the condition that the number of the service interfaces to be called is greater than or equal to a preset number threshold, inquiring a service interface mapping table by the service identifier to obtain a converged service interface, wherein the service interface mapping table comprises: the mapping relation between the service identifier of each financial service and the corresponding converged service interface is an interface obtained after the service interfaces to be invoked are converged; and calling the fusion service interface to execute the target financial service.
Optionally, before resolving the service call request sent by the user side, the method further includes: acquiring call flow information of N service interfaces to be called for executing the historical financial service based on the historical service call request, wherein N is a positive integer greater than or equal to 2; arranging N service interfaces to be called based on the call flow information to generate service interface arrangement information; converting the service interface arrangement information into an executable program; and packaging the executable program into a program package, and generating a call entry capable of calling the program package to obtain the fusion service interface.
Optionally, after obtaining the converged service interface, the method further includes: and establishing the service interface mapping table based on the service identification of the associated history financial service in the history service call request and the fusion service interface.
Optionally, after acquiring call flow information of the N service interfaces to be invoked for executing the historical financial service based on the historical service call request, the method further includes: based on the service call request, obtaining access information of each service interface to be called, wherein the access information at least comprises: interface identification, interface name, public key information, private key information; and carrying out signature verification based on the public key information, wherein the signature verification is used for verifying whether a user using the user terminal is in a usable list, and the usable list is generated when each service interface to be called is created.
Optionally, the step of arranging N service interfaces to be invoked based on the invoking flow information to generate service interface arranging information includes: and providing a visual service interface arrangement interface for a service end, wherein the service interface arrangement interface comprises visual nodes and visual connecting lines, and the service end connects the visual nodes corresponding to the service interface to be called according to the call flow information and the visual connecting lines to generate the service interface arrangement information.
Optionally, after converting the service interface arrangement information into an executable program, the method further comprises: running the executable program in a sandbox; monitoring the running executable program and recording monitoring information in real time; and under the condition that abnormal information exists in the monitoring information, sending the abnormal information, and calling a preset abnormal processing module to perform error rollback operation, wherein the error rollback operation refers to the operation of recovering the executable program to the correct state at the last time.
Optionally, the step of encapsulating the executable program into a program package and providing a call entry to obtain the converged service interface includes: encapsulating the executable program to obtain the program package; and creating a service interface instance based on the program package, and creating a call entry for the service interface instance to obtain the converged service interface.
Optionally, the calling method further includes: checking the user identity using the user terminal under the condition that the number of the service interfaces to be called is smaller than the preset number threshold; under the condition that the user identity of the user terminal passes verification, acquiring a target data format based on the service call request; and creating a service interface conversion strategy based on the target data format, wherein the service interface conversion strategy is used for converting the service interface to be called into an interface corresponding to the target data format.
According to another aspect of the embodiment of the present invention, there is also provided a calling device for fusing service interfaces, including: the system comprises an analysis unit, a service calling unit and a service processing unit, wherein the analysis unit is used for analyzing a service calling request sent by a user side, and determining the number of service interfaces to be called based on the service calling request, wherein the service calling request carries a service identifier of a target financial service to be executed; the query unit is configured to query a service interface mapping table by the service identifier to obtain a converged service interface when the number of service interfaces to be invoked is greater than or equal to a preset number threshold, where the service interface mapping table includes: the mapping relation between the service identifier of each financial service and the corresponding converged service interface is an interface obtained after the service interfaces to be invoked are converged; and the calling unit is used for calling the fusion service interface to execute the target financial service.
Optionally, the calling device of the converged service interface further includes: the first acquisition module is used for acquiring call flow information of N service interfaces to be called for executing the historical financial service based on the historical service call request, wherein N is a positive integer greater than or equal to 2; the first arrangement module is used for arranging N service interfaces to be called based on the call flow information to generate service interface arrangement information; the first conversion module is used for converting the service interface arrangement information into an executable program; and the first encapsulation module is used for encapsulating the executable program into a program package, and generating a call entry capable of calling the program package to obtain the fusion service interface.
Optionally, the calling device of the converged service interface further includes: the first establishing module is used for establishing the service interface mapping table based on the service identification of the associated history financial service in the history service call request and the fusion service interface.
Optionally, the calling device of the converged service interface further includes: the second obtaining module is configured to obtain, based on the service invocation request, access information of each service interface to be invoked, where the access information at least includes: interface identification, interface name, public key information, private key information; and the first verification module is used for carrying out signature verification based on the public key information, wherein the signature verification is used for verifying whether a user using the user terminal is in a usable list, and the usable list is generated when each service interface to be called is created.
Optionally, the first orchestration module comprises: the service terminal is used for connecting the visual nodes corresponding to the service interface to be called according to the calling flow information and generating the service interface arrangement information.
Optionally, the calling device of the converged service interface further includes: the first execution module is used for running the executable program in the sandbox; the first monitoring module is used for monitoring the running executable program and recording monitoring information in real time; the first sending module is used for sending the abnormal information under the condition that the abnormal information exists in the monitoring information, and calling a preset abnormal processing module to perform error rollback operation, wherein the error rollback operation is an operation for recovering the executable program to a correct state at the last time.
Optionally, the first packaging module includes: the first encapsulation submodule is used for encapsulating the executable program to obtain the program package; and the first creation sub-module is used for creating a service interface instance based on the program package, and creating a call entry for the service interface instance to obtain the fusion service interface.
Optionally, the calling device of the converged service interface further includes: the second checking module is used for checking the user identity using the user terminal under the condition that the number of the service interfaces to be called is smaller than the preset number threshold; the third acquisition module is used for acquiring a target data format based on the service call request under the condition that the user identity of the user terminal passes verification; the first creating module is used for creating a service interface conversion strategy based on the target data format, wherein the service interface conversion strategy is used for converting the service interface to be called into an interface corresponding to the target data format.
According to another aspect of the embodiment of the present invention, there is further provided a computer readable storage medium, where the computer readable storage medium includes a stored computer program, where when the computer program runs, the device where the computer readable storage medium is controlled to execute the method for calling any one of the fusion service interfaces described above.
According to another aspect of the embodiment of the present invention, there is also provided an electronic device, including one or more processors and a memory, where the memory is configured to store one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement a method for calling any one of the fusion service interfaces described above.
In the present disclosure, the method comprises the following steps: firstly analyzing a service call request sent by a user side, determining the number of service interfaces to be called based on the service call request, then inquiring a service interface mapping table by a service identifier under the condition that the number of the service interfaces to be called is greater than or equal to a preset number threshold value to obtain a converged service interface, and finally calling the converged service interface to execute target financial service.
In the present disclosure, when a service call request indicates that a plurality of service interfaces need to be called for service processing, a fusion service interface needing to be called is determined by querying a service interface mapping table, and a service interface which is fused in advance is called for executing financial service.
In the method, each service interface in the system is displayed through a visual interface, the service interfaces are arranged through interface nodes and connecting wires to form a complete service interface calling chain, background automatically converts arrangement information into executable programs, packages the executable programs into program packages, then places the program packages into sandboxes for operation and testing, and the fused service interfaces are obtained, and when related service requests are received, the fused interfaces are directly called to carry out service processing.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiments of the invention and together with the description serve to explain the invention and do not constitute a limitation on the invention. In the drawings:
FIG. 1 is a flow chart of an alternative converged service interface invocation method in accordance with an embodiment of the present invention;
FIG. 2 is a flow chart of an alternative orchestration method for converged service interfaces according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of an alternative converged service interface calling device in accordance with an embodiment of the present invention;
fig. 4 is a block diagram of a hardware structure of an electronic device (or mobile device) that fuses calling methods of service interfaces according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented 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.
To facilitate an understanding of the invention by those skilled in the art, some terms or nouns involved in the various embodiments of the invention are explained below:
a subset of the extensible markup language, extensible Markup Language, XML for short, standard generic markup language may be used to tag data, define data types.
The JS object numbered musical notation JavaScript Object Notation, JSON for short, is a lightweight data exchange format.
YAML, a highly readable format for expressing data serialization.
The software operation service Software as a Service, abbreviated as SaaS, refers to a new form of obtaining a software service by a user, and the user obtains the service with corresponding software function required by the user directly from a special provider through a network according to a certain Service Level Agreement (SLA).
An application programming interface, applicatiuon Programming Interface, an API for short, provides the ability for applications and developers to access a set of routines based on some software or hardware.
It should be noted that, the method and the device for calling the converged service interface in the present disclosure may be used in the cloud computing technical field when the converged service interface is called, and may also be used in any field other than the cloud computing technical field when the converged service interfaces are fused and called, and the application field of the method and the device for calling the converged service interface in the present disclosure is not limited.
It should be noted that, related information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present disclosure are information and data authorized by a user or sufficiently authorized by each party, and the collection, use and processing of related data need to comply with related laws and regulations and standards of related countries and regions, and be provided with corresponding operation entries for the user to select authorization or rejection. For example, an interface is provided between the system and the relevant user or institution, before acquiring the relevant information, the system needs to send an acquisition request to the user or institution through the interface, and acquire the relevant information after receiving the consent information fed back by the user or institution.
The embodiments of the invention can be applied to various interface calling systems/applications/devices, the interfaces to be called and the interface calling flow are determined based on the service request, the interfaces to be called are arranged in the visual interface to obtain arrangement information, the arrangement information is converted into executable programs and put into a sandbox to operate to obtain the fused service interface, and the fused service interface is directly called according to the request content when the service request is processed, so that the service flow is simplified and the service processing efficiency is improved.
The present invention will be described in detail with reference to the following examples.
Example 1
According to an embodiment of the present invention, there is provided an embodiment of a calling method of a converged service interface, it being noted that the steps shown in the flowcharts of the drawings may be performed in a computer system such as a set of computer executable instructions, and that although a logical order is shown in the flowcharts, in some cases the steps shown or described may be performed in an order different from that herein.
FIG. 1 is a flowchart of an alternative converged service interface invocation method, as shown in FIG. 1, according to an embodiment of the present invention, the method comprising the steps of:
Step S101, analyzing a service call request sent by a user terminal, and determining the number of service interfaces to be called based on the service call request, wherein the service call request carries a service identifier of a target financial service to be executed;
step S102, under the condition that the number of the service interfaces to be called is larger than or equal to a preset number threshold, a service identifier queries a service interface mapping table to obtain a converged service interface, wherein the service interface mapping table comprises: the mapping relation between the service identifier of each financial service and the corresponding fusion service interface, wherein the fusion service interface is an interface obtained after fusion of all the service interfaces to be called;
step S103, calling a fusion service interface to execute the target financial service.
Through the steps, firstly, the service call request sent by the user terminal is analyzed, the number of service interfaces to be called is determined based on the service call request, then, under the condition that the number of the service interfaces to be called is greater than or equal to a preset number threshold value, the service identifier queries the service interface mapping table to obtain the fusion service interface, and finally, the fusion service interface is called to execute the target financial service.
In this embodiment, when a service call request indicates that a plurality of service interfaces need to be called for service processing, a service interface mapping table is queried to determine a fusion service interface to be called, and a service interface which is fused in advance is called to execute financial service.
Embodiments of the present invention will be described in detail with reference to the following steps.
It should be noted that, in the embodiment of the invention, the service interfaces are arranged through the visual interface to form a complete call chain, and a plurality of interfaces corresponding to the call chain are fused into one service interface, so that the interface call flow is simplified, and the service processing efficiency is improved.
Optionally, before resolving a service call request sent by a user side, a converged service interface needs to be acquired first, and fig. 2 is a flowchart of an arrangement method of an optional converged service interface according to an embodiment of the present invention, as shown in fig. 2, where the method includes the following steps:
step S201, based on the history service call request, obtaining call flow information of N service interfaces to be called for executing the history financial service, wherein N is a positive integer greater than or equal to 2.
It should be noted that, in the embodiment of the present invention, a plurality of service interfaces are fused in advance according to a history service call request, and the fused service interfaces correspond to one or more financial services.
Optionally, after executing the call flow information of the N service interfaces to be invoked of the historical financial service based on the historical service call request, the method further includes: based on the service calling request, access information of each service interface to be called is obtained, wherein the access information at least comprises: interface identification, interface name, public key information, private key information; and carrying out signature verification based on the public key information, wherein the signature verification is used for verifying whether a user using the user terminal is in a usable list, and the usable list is generated when each service interface to be called is created.
Before the service interface is called, the user of the interface needs to be checked first to verify whether the user exists in the usable list, obtain the access information of the service interface provided by the service party, check according to the public key information in the access information of the service interface, and prompt error information if the user does not exist in the usable list.
Step S202, arranging N service interfaces to be called based on the call flow information, and generating service interface arrangement information.
Optionally, the step of arranging the N service interfaces to be invoked based on the invoking flow information to generate service interface arranging information includes: and providing a visual service interface arrangement interface for the service end, wherein the service interface arrangement interface comprises visual nodes and visual connecting lines, and the service end connects the visual nodes corresponding to the service interface to be called according to the visual connecting lines according to the call flow information to generate service interface arrangement information.
It should be noted that, in the embodiment of the invention, all service interfaces of the system are displayed through the visual interface arrangement interface, service personnel determine the service interface to be invoked and the corresponding invoking flow according to the service invoking request, select the corresponding interface node and connecting line in the visual arrangement interface, arrange the interface node according to the invoking flow to form a complete invoking chain, and generate the corresponding service interface arrangement information.
Optionally, after the interfaces are arranged, a plurality of interfaces are required to be fused into one interface, when the interfaces are fused, a first service interface is called, logic judgment is performed to obtain a first return field of a first service interface node, then a second service interface is called to perform logic judgment and obtain a second return field of a second service interface node, and then the first return field and the second return field are recombined to obtain a new field name, an object name and a data type, so that a fused new field is obtained.
Step S203, the service interface arrangement information is converted into an executable program.
Optionally, after converting the service interface arrangement information into the executable program, further comprising: running an executable program in a sandbox; monitoring the running executable program and recording monitoring information in real time; and under the condition that the abnormal information exists in the monitoring information, the abnormal information is sent, and a preset abnormal processing module is called to perform error rollback operation, wherein the error rollback operation refers to the operation of recovering the executable program to the correct state at the last time.
It should be noted that, after the executable program is obtained, the feasibility of the program needs to be tested first, and in this embodiment, the executable program is put into a sandbox to run, so that the process of applying for a server and deploying an operating environment is omitted, and the running in the sandbox does not affect the use of other interfaces in the system.
It should be noted that, the exception during the program running process includes, but is not limited to: when the abnormal information is captured, the abnormal information can be sent in a mail/short message/call mode and rollback operation is carried out, so that the executable program returns to the last correct state.
Optionally, when the executable program is run, the embodiment of the invention creates the running log based on the running condition, and for the fusion service interface which is not on line, the running log can be directly checked through the arrangement interface, and for the fusion service interface which is on line, the running log can be queried through the self-service development platform.
Step S204, the executable program is packaged into a program package, and a call entry capable of calling the program package is generated, so that a fusion service interface is obtained.
Optionally, the step of encapsulating the executable program into a program package and providing a call portal to obtain a converged service interface includes: packaging the executable program to obtain a program package; and creating a service interface instance based on the program package, and creating a call entry for the service interface instance to obtain a converged service interface.
After the sandbox test operation is passed, the executable program needs to be packaged into a program package, when the fusion service interface is called for the first time, a fusion service interface instance needs to be created, when the instance creation is carried out, a reserved instance resident system can be selected, or an unreserved instance can be selected, when the instance is called for increasing, the instance is created, and when the instance is called for decreasing, the instance is destroyed.
Optionally, after obtaining the converged service interface, the method further includes: and establishing a service interface mapping table based on the service identification and the fusion service interface of the associated history financial service in the history service call request.
It should be noted that, in order to facilitate the subsequent direct use of the converged service interface, it is necessary to create a mapping relationship between the service interface and the service, and establish a service interface mapping table, and then, when receiving the same service request, directly query the service interface mapping table to obtain the converged service interface to be invoked, and if there is no corresponding converged service interface, schedule the interface in real time and add the converged service interface.
Step S101, analyzing a service call request sent by a user terminal, and determining the number of service interfaces to be called based on the service call request, wherein the service call request carries a service identifier of a target financial service to be executed.
It should be noted that, the implementation main body of the embodiment of the present invention is a server, the server establishes a connection with a user terminal, the user terminal selects a corresponding service, generates a service call request, the service call request carries information such as a service identifier, a service name, etc., and after receiving the service call request sent by the user terminal, the server allocates a corresponding service interface for the service, and each service call request needs to call one or more service interfaces.
Step S102, under the condition that the number of the service interfaces to be called is larger than or equal to a preset number threshold, a service identifier queries a service interface mapping table to obtain a converged service interface, wherein the service interface mapping table comprises: the mapping relation between the service identification of each financial service and the corresponding fusion service interface is obtained after all the service interfaces to be called are fused.
When a service indicates that a plurality of financial service interfaces need to be called, a fusion service interface corresponding to the service can be obtained by querying a service interface mapping table under the condition that the number of the financial service interfaces is larger than a preset number threshold, and when a service interface which is fused in advance is not queried, a plurality of interfaces to be called can be arranged and packaged to obtain a new fusion service interface.
Step S103, calling a fusion service interface to execute the target financial service.
It should be noted that, the service interface after fusion contains field information of all the interfaces to be invoked originally, and the financial service which can be completed only by common execution of the plurality of interfaces originally can be executed.
Through the steps, the different interface nodes are arranged, processed and fused, the arranged flow is converted into an executable program and is packaged to obtain a package, and an instance is created for the packaged interface and an access entry or an access address is provided for the user side to access.
Optionally, the calling method of the converged service interface further includes: under the condition that the number of the service interfaces to be called is smaller than a preset number threshold, checking the user identity of the user terminal; under the condition that the user identity of the user side passes the verification, acquiring a target data format based on the service call request; and creating a service interface conversion strategy based on the target data format, wherein the service interface conversion strategy is used for converting the service interface to be called into an interface corresponding to the target data format.
It should be noted that, when the number of interfaces to be called is smaller than the preset number threshold, the interfaces can be directly called, before the calling, the data formats of the user and the service party, especially in a financial system, need to be judged, and the data can be stored in various forms when being stored, when the data format of the user is different from the data format of the service party, format conversion needs to be performed on the interfaces to be called, so that the format required by the data service user output by the interfaces, for example, the conversion of time includes millisecond, second, hour, day conversion and different date and time formats, the conversion of the amount supports the fractional retention digit, digit complement, case conversion and the conversion of the data supports the conversion of formats such as xml, json, yaml.
Alternatively, the embodiment can be applied to arranging the SaaS-API to form a complete call chain and an exception handling mechanism, and the response value is obtained through sandbox operation and the incoming interface characteristic information, so that quick online is supported, and the exception reminds an application user through the handling mechanism.
Optionally, after the visual interface is edited through the nodes and the connecting lines, after the interface is arranged, jrjz.getrun link (a function used for acquiring the running link of the current page) is used for converting the arrangement information into an executable program, in the calling process, a logic node is used for editing branches and transmitting processing parameters, a response value can be customized, and finally the executable program is put into a sandbox to run, so that multiple calling, processing and fusion among different SaaS-APIs are completed, and the fused SaaS-APIs are obtained.
Optionally, when the jrjz.getlink is used to run the call link, jrjz.dealerror (an exception handling function is used to process exception information) is used to automatically perform error rollback on a specific exception, record execution error information, and other APIs can be called and send a message of a router MQ (an open source distributed message middleware) and a mail mode to achieve display and notification of the exception.
In the field of SaaS application, the SaaS product may implement delivery of its service by providing a set of APIs to the user, where the SaaS-API interfacing is responsible for connection service and re-task of transmitting data, data transmission and operation including sensitive information and important data, and formulation links of various service policies, etc.
Optionally, when the interface is converted, saaS-API node editing is performed through a visual interface, back-end automatic processing is performed, jrjz.typeConverter (type conversion function for converting character strings into specified types) is called during processing, data are automatically identified and converted, and feature information is set through jrjz.setApp (setting function for setting names and version numbers of application programs) mainly for processing of amount, time and data exchange formats, and then the original interface is modified and directly called to be put into application.
After the fused SaaS-API is obtained, an user can call the getClient method (an interface calling method) in the SaaS-API in a code, write parameters and inheritors according to requirements in request parameters and response parameters, complete single call, repeat for a plurality of times and increase logic processing in the middle; the user can also obtain the latest version of the SaaS-API registration through a jrjz.getkey method (an interface calling method), update parameter configuration and inheritors to be filled in, automatically complete adjustment of request parameters and response parameters of single or multiple calls, and ensure the usability and safety of multiple calls of the SaaS-API through unified processing of anomalies defined by the application by a standardized reminding and processing mode.
In the above embodiment, the interface to be invoked is arranged on the visual interface to obtain the arrangement information, the arrangement information is converted into the executable program, and the executable program is put into the sandbox to run to obtain the fused service interface, and when the service request is processed, the fused service interface is directly invoked according to the request content, so that the service flow is simplified, and the service processing efficiency is improved.
The following describes in detail another embodiment.
Example two
The calling device of the converged service interface provided in the present embodiment includes a plurality of implementation units, and each implementation unit corresponds to each implementation step in the first embodiment.
FIG. 3 is a schematic diagram of an alternative converged service interface calling device according to an embodiment of the present invention, and as shown in FIG. 3, the converged service interface calling device may include: a parsing unit 31, a querying unit 32, a calling unit 33, wherein,
the parsing unit 31 is configured to parse a service call request sent by a user terminal, and determine the number of service interfaces to be called based on the service call request, where the service call request carries a service identifier of a target financial service to be executed;
the query unit 32 is configured to query, by the service identifier, a service interface mapping table to obtain a converged service interface when the number of service interfaces to be invoked is greater than or equal to a preset number threshold, where the service interface mapping table includes: the mapping relation between the service identifier of each financial service and the corresponding fusion service interface, wherein the fusion service interface is an interface obtained after fusion of all the service interfaces to be called;
And the calling unit 33 is used for calling the fusion service interface to execute the target financial service.
The above-mentioned call device for converged service interfaces analyzes the service call request sent by the user terminal through the analysis unit 31, and determines the number of service interfaces to be called based on the service call request, where the service call request carries the service identifier of the target financial service to be executed; under the condition that the number of the service interfaces to be called is greater than or equal to a preset number threshold value, the service identifier queries the service interface mapping table to obtain a converged service interface through the query unit 32; the fusion service interface is called by the calling unit 33 to execute the target financial service.
In this embodiment, when a service call request indicates that a plurality of service interfaces need to be called for service processing, a service interface mapping table is queried to determine a fusion service interface to be called, and a service interface which is fused in advance is called to execute financial service.
Optionally, the calling device of the converged service interface further includes: the first acquisition module is used for acquiring call flow information of N service interfaces to be called for executing the historical financial service based on the historical service call request, wherein N is a positive integer greater than or equal to 2; the first arrangement module is used for arranging N service interfaces to be called based on the call flow information to generate service interface arrangement information; the first conversion module is used for converting the service interface arrangement information into an executable program; and the first encapsulation module is used for encapsulating the executable program into a program package, and generating a call entry capable of calling the program package to obtain the fusion service interface.
Optionally, the calling device of the converged service interface further includes: the first establishing module is used for establishing a service interface mapping table based on the service identification and the fusion service interface of the associated history financial service in the history service calling request.
Optionally, the calling device of the converged service interface further includes: the second obtaining module is configured to obtain, based on the service invocation request, access information of each service interface to be invoked, where the access information at least includes: interface identification, interface name, public key information, private key information; and the first verification module is used for carrying out signature verification based on the public key information, wherein the signature verification is used for verifying whether a user using the user terminal is in a usable list, and the usable list is generated when each service interface to be called is created.
Optionally, the first orchestration module comprises: the service terminal is used for connecting the visual nodes corresponding to the service interface to be called according to the visual connecting lines and generating service interface arrangement information.
Optionally, the calling device of the converged service interface further includes: the first execution module is used for running an executable program in the sandbox; the first monitoring module is used for monitoring the running executable program and recording monitoring information in real time; the first sending module is used for sending the abnormal information under the condition that the abnormal information exists in the monitoring information, and calling the preset abnormal processing module to perform error rollback operation, wherein the error rollback operation is an operation for recovering the executable program to the correct state at the last time.
Optionally, the first packaging module includes: the first encapsulation submodule is used for encapsulating the executable program to obtain a program package; the first creation sub-module is used for creating a service interface instance based on the program package, and creating a call entry for the service interface instance to obtain a fusion service interface.
Optionally, the calling device of the converged service interface further includes: the second checking module is used for checking the user identity of the user terminal under the condition that the number of the service interfaces to be called is smaller than a preset number threshold value; the third acquisition module is used for acquiring a target data format based on the service call request under the condition that the user identity of the user side passes verification; the first creating module is used for creating a service interface conversion strategy based on the target data format, wherein the service interface conversion strategy is used for converting the service interface to be called into an interface corresponding to the target data format.
The calling device of the fusion service interface may further include a processor and a memory, where the parsing unit 31, the querying unit 32, the calling unit 33, and the like are stored as program units in the memory, and the processor executes the program units stored in the memory to implement corresponding functions.
The processor includes a kernel, and the kernel fetches a corresponding program unit from the memory. The kernel can be provided with one or more than one, and the kernel parameters are adjusted to fuse and call the plurality of service interfaces.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM), which includes at least one memory chip.
According to another aspect of the embodiment of the present invention, there is also provided a computer readable storage medium, where the computer readable storage medium includes a stored computer program, and when the computer program runs, a device where the computer readable storage medium is located is controlled to execute a method for calling any one of the fusion service interfaces described above.
According to another aspect of the embodiment of the present invention, there is also provided an electronic device, including one or more processors and a memory, where the memory is configured to store one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors implement a method for calling any one of the fusion service interfaces described above.
The present application also provides a computer program product adapted to perform, when executed on a data processing device, a program initialized with the method steps of: analyzing a service call request sent by a user side, and determining the number of service interfaces to be called based on the service call request, wherein the service call request carries a service identifier of a target financial service to be executed; under the condition that the number of the service interfaces to be called is greater than or equal to a preset number threshold, a service identifier queries a service interface mapping table to obtain a converged service interface, wherein the service interface mapping table comprises: the mapping relation between the service identifier of each financial service and the corresponding fusion service interface, wherein the fusion service interface is an interface obtained after fusion of all the service interfaces to be called; and calling the fusion service interface to execute the target financial service.
Fig. 4 is a block diagram of a hardware structure of an electronic device (or mobile device) that fuses calling methods of service interfaces according to an embodiment of the present invention. As shown in fig. 4, the electronic device may include one or more (shown in fig. 4 as 402a, 402b, … …,402 n) processors 402 (the processors 402 may include, but are not limited to, a microprocessor MCU, a programmable logic device FPGA, etc. processing means), a memory 404 for storing data. In addition, the method may further include: a display, an input/output interface (I/O interface), a Universal Serial Bus (USB) port (which may be included as one of the ports of the I/O interface), a network interface, a keyboard, a power supply, and/or a camera. It will be appreciated by those of ordinary skill in the art that the configuration shown in fig. 4 is merely illustrative and is not intended to limit the configuration of the electronic device described above. For example, the electronic device may also include more or fewer components than shown in FIG. 4, or have a different configuration than shown in FIG. 4.
The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
In the foregoing embodiments of the present invention, the descriptions of the embodiments are emphasized, and for a portion of this disclosure that is not described in detail in this embodiment, reference is made to the related descriptions of other embodiments.
In the several embodiments provided in the present application, it should be understood that the disclosed technology content may be implemented in other manners. The above-described embodiments of the apparatus are merely exemplary, and the division of the units, for example, may be a logic function division, and may be implemented in another manner, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interfaces, units or modules, or may be in electrical or other forms.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied essentially or in part or all of the technical solution or in part in the form of a software product stored in a storage medium, including instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely a preferred embodiment of the present invention and it should be noted that modifications and adaptations to those skilled in the art may be made without departing from the principles of the present invention, which are intended to be comprehended within the scope of the present invention.
Claims (11)
1. A method for invoking a converged service interface, comprising:
analyzing a service call request sent by a user side, and determining the number of service interfaces to be called based on the service call request, wherein the service call request carries a service identifier of a target financial service to be executed;
and under the condition that the number of the service interfaces to be called is greater than or equal to a preset number threshold, inquiring a service interface mapping table by the service identifier to obtain a converged service interface, wherein the service interface mapping table comprises: the mapping relation between the service identifier of each financial service and the corresponding converged service interface is an interface obtained after the service interfaces to be invoked are converged;
and calling the fusion service interface to execute the target financial service.
2. The method for invoking as claimed in claim 1, further comprising, prior to parsing the service invocation request sent by the client:
acquiring call flow information of N service interfaces to be called for executing the historical financial service based on the historical service call request, wherein N is a positive integer greater than or equal to 2;
arranging N service interfaces to be called based on the call flow information to generate service interface arrangement information;
Converting the service interface arrangement information into an executable program;
and packaging the executable program into a program package, and generating a call entry capable of calling the program package to obtain the fusion service interface.
3. The method of claim 2, further comprising, after obtaining the converged service interface:
and establishing the service interface mapping table based on the service identification of the associated history financial service in the history service call request and the fusion service interface.
4. The method according to claim 2, further comprising, after executing call flow information of N of the service interfaces to be invoked of the history financial service based on the history service call request:
based on the service call request, obtaining access information of each service interface to be called, wherein the access information at least comprises: interface identification, interface name, public key information, private key information;
and carrying out signature verification based on the public key information, wherein the signature verification is used for verifying whether a user using the user terminal is in a usable list, and the usable list is generated when each service interface to be called is created.
5. The calling method according to claim 2, wherein the step of arranging N of the service interfaces to be called based on the call flow information to generate service interface arrangement information includes:
and providing a visual service interface arrangement interface for a service end, wherein the service interface arrangement interface comprises visual nodes and visual connecting lines, and the service end connects the visual nodes corresponding to the service interface to be called according to the call flow information and the visual connecting lines to generate the service interface arrangement information.
6. The method of claim 2, further comprising, after converting the service interface orchestration information into an executable program:
running the executable program in a sandbox;
monitoring the running executable program and recording monitoring information in real time;
and under the condition that abnormal information exists in the monitoring information, sending the abnormal information, and calling a preset abnormal processing module to perform error rollback operation, wherein the error rollback operation refers to the operation of recovering the executable program to the correct state at the last time.
7. The method of claim 2, wherein the step of encapsulating the executable program into a package and providing a call portal to obtain the converged service interface comprises:
encapsulating the executable program to obtain the program package;
and creating a service interface instance based on the program package, and creating a call entry for the service interface instance to obtain the converged service interface.
8. The calling method of claim 1, further comprising:
checking the user identity using the user terminal under the condition that the number of the service interfaces to be called is smaller than the preset number threshold;
under the condition that the user identity of the user terminal passes verification, acquiring a target data format based on the service call request;
and creating a service interface conversion strategy based on the target data format, wherein the service interface conversion strategy is used for converting the service interface to be called into an interface corresponding to the target data format.
9. A converged service interface invoking device, comprising:
the system comprises an analysis unit, a service calling unit and a service processing unit, wherein the analysis unit is used for analyzing a service calling request sent by a user side, and determining the number of service interfaces to be called based on the service calling request, wherein the service calling request carries a service identifier of a target financial service to be executed;
The query unit is configured to query a service interface mapping table by the service identifier to obtain a converged service interface when the number of service interfaces to be invoked is greater than or equal to a preset number threshold, where the service interface mapping table includes: the mapping relation between the service identifier of each financial service and the corresponding converged service interface is an interface obtained after the service interfaces to be invoked are converged;
and the calling unit is used for calling the fusion service interface to execute the target financial service.
10. A computer readable storage medium, characterized in that the computer readable storage medium comprises a stored computer program, wherein the computer program when run controls a device in which the computer readable storage medium is located to execute the method for invoking the converged service interface according to any one of claims 1 to 8.
11. An electronic device comprising one or more processors and a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of invoking the fusion service interface of any of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310371209.8A CN116483899A (en) | 2023-04-07 | 2023-04-07 | Calling method and device for converged service interface, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310371209.8A CN116483899A (en) | 2023-04-07 | 2023-04-07 | Calling method and device for converged service interface, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116483899A true CN116483899A (en) | 2023-07-25 |
Family
ID=87220552
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310371209.8A Pending CN116483899A (en) | 2023-04-07 | 2023-04-07 | Calling method and device for converged service interface, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116483899A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117742900A (en) * | 2024-02-05 | 2024-03-22 | 北京优特捷信息技术有限公司 | Method, device, equipment and storage medium for constructing service call graph |
| CN117742900B (en) * | 2024-02-05 | 2024-05-14 | 北京优特捷信息技术有限公司 | Method, device, equipment and storage medium for constructing service call graph |
-
2023
- 2023-04-07 CN CN202310371209.8A patent/CN116483899A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117742900A (en) * | 2024-02-05 | 2024-03-22 | 北京优特捷信息技术有限公司 | Method, device, equipment and storage medium for constructing service call graph |
| CN117742900B (en) * | 2024-02-05 | 2024-05-14 | 北京优特捷信息技术有限公司 | Method, device, equipment and storage medium for constructing service call graph |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108415832B (en) | Interface automation test method, device, equipment and storage medium | |
| US10089082B2 (en) | Visual devops systems and methods | |
| CN111045756B (en) | Method, apparatus, computing device and medium for generating interface service | |
| CN110275831B (en) | Mock data verification method and device of protocol interface | |
| CN108628748B (en) | Automatic test management method and automatic test management system | |
| CN113014475B (en) | Message pushing integration method and device | |
| CN110289983B (en) | Load balancing application creation method and device, computer equipment and storage medium | |
| CN111143087A (en) | Interface calling method and device, storage medium and server | |
| JP2019512138A (en) | Service implementation method, apparatus and system based on FIX protocol | |
| CN111949899B (en) | Service integration method and service platform | |
| CN112835782B (en) | Interface access test method and system | |
| CN110851471A (en) | Distributed log data processing method, device and system | |
| CN111708632A (en) | Cloud resource management method and device | |
| CN113687858A (en) | Configuration file checking method and device, electronic equipment and storage medium | |
| CN113127108A (en) | Service request processing method and device, storage medium and electronic equipment | |
| CN113918232B (en) | Algorithm service calling method, device, server and storage medium | |
| CN111752820A (en) | Pressure testing method of gPC interface, computer equipment and storage medium | |
| CN112527459A (en) | Log analysis method and device based on Kubernetes cluster | |
| CN116483899A (en) | Calling method and device for converged service interface, electronic equipment and storage medium | |
| CN116346660A (en) | Data processing method, device, equipment and medium based on dependent replacement service | |
| CN109816462A (en) | A kind of recognition methods of invoice information and device | |
| CN114428723A (en) | Test system, system test method, related device and storage medium | |
| CN113742235A (en) | Method and device for checking codes | |
| CN115543491A (en) | Microservice processing method and device | |
| CN112069078A (en) | ESA interface pressure testing method, device, testing equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |