CN116668520A - Gateway-based service arrangement method, system, equipment and storage medium - Google Patents
Gateway-based service arrangement method, system, equipment and storage medium Download PDFInfo
- Publication number
- CN116668520A CN116668520A CN202310496267.3A CN202310496267A CN116668520A CN 116668520 A CN116668520 A CN 116668520A CN 202310496267 A CN202310496267 A CN 202310496267A CN 116668520 A CN116668520 A CN 116668520A
- Authority
- CN
- China
- Prior art keywords
- service
- information
- api
- target
- orchestration
- 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 46
- 238000012545 processing Methods 0.000 claims description 10
- 238000013515 script Methods 0.000 claims description 9
- 230000005540 biological transmission Effects 0.000 claims description 8
- 230000008569 process Effects 0.000 claims description 7
- 230000002452 interceptive effect Effects 0.000 claims description 2
- 238000011161 development Methods 0.000 abstract description 2
- 238000004590 computer program Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000004458 analytical method Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000000452 restraining effect Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 238000012800 visualization Methods 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/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/303—Terminal profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/14—Network analysis or design
- H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
-
- 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/01—Protocols
- H04L67/133—Protocols for remote procedure calls [RPC]
-
- 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 application discloses a gateway-based service arrangement method, which comprises the steps of exposing and restricting service information and API port information provided by each service end to obtain corresponding registration information; according to the registration information, the execution logic of each server side API interface and the execution sequence between the server side API interfaces, configuring and generating a service arrangement file; constructing a service arrangement model based on the service arrangement file of the service end; and analyzing the service arrangement model according to the service request sent by the application end to obtain a corresponding service list. The application also provides a service arrangement system, equipment and a storage medium. The method provided by the application can effectively improve the development work efficiency of real service arrangement.
Description
Technical Field
The present application relates to the field of computers, and in particular, to a gateway-based service orchestration method, system, device, and storage medium.
Background
In a new era, public service digitization has become a new direction of public service transformation, and only if the internal informatization level is continuously improved, better service can be provided. With the introduction of cloud computing technology, the construction of efficient and stable informatization systems has become a necessary requirement for public service providers. However, the public service providers respectively build own informationized systems, so that the problems of access, complex flow and the like of different services are caused, and the use difficulty of the public service is greatly improved.
At present, most of service arrangement realization methods are to write related codes in the background for data service combination through service requirements, so as to realize corresponding services.
Patent document CN111078315B discloses a micro-service orchestration, execution method and system, architecture, device, storage medium, the micro-service orchestration method comprising: according to a preset micro-service arrangement template, based on a target service end combination and a logic relation between target service ends in the target service end combination, configuring and generating a micro-service arrangement file, wherein the configuration content of the micro-service arrangement file comprises: the identification information, the input parameter information, the target server interface information, the execution logic of the target server interface and the execution sequence information between the target server interfaces of the micro service orchestration file, and the output result information; analyzing the micro-service orchestration file generated by configuration, and dynamically generating a corresponding executable script; and loading the executable script into a JAVA virtual machine for execution. The method does not provide specific rule constraints, and errors exist in the arrangement process.
Patent document CN114237628A discloses a method, device, computer equipment and storage medium for micro-service orchestration and invocation, the method implementation of which comprises: carrying out standardized acquisition on capability data of micro-services to be arranged; performing imaging process arrangement on the acquired capacity data of the micro service to be arranged; registering the arranged flow by a scheduling engine and starting an instance; generating an agent program corresponding to the micro-service to be arranged according to the collected capability data of the micro-service to be arranged, compiling the agent program through a tool chain to generate a mirror image package, and distributing the mirror image package to a container platform; when a call request is monitored, the scheduling engine sends a call instruction to a corresponding agent program according to a preset call rule so as to realize the call of the arranged flow.
Disclosure of Invention
In order to solve the problems, the application provides a gateway-based service arrangement method, which can effectively improve the development work efficiency of real service arrangement.
A gateway-based service orchestration method, the gateway being configured to associate a plurality of servers and applications, the service orchestration method comprising the steps of:
and exposing and restricting the service information and the API port information provided by each service end to obtain corresponding registration information.
And configuring and generating a service arrangement file according to the registration information, the execution logic of each service end API interface and the execution sequence between the service end API interfaces, wherein the configuration content of the service arrangement file comprises identification information of the service arrangement file, input parameter information, target service end API interface information, the execution logic of the target service end API interface and the execution sequence between the service end API interfaces, and output result information.
And constructing a corresponding service arrangement model based on the service arrangement file of the service end.
And analyzing the service arrangement model according to the service request sent by the application end to obtain a corresponding service list.
The application registers all the service terminals based on the API interface and provides the arrangement relation of each service terminal in advance, thereby quickly constructing the execution logic relation among each service terminal in the follow-up actual arrangement process so as to obtain the optimal service list.
Specifically, the API port information is sequentially subjected to constraint registration according to parameters, calling modes and name information sequences.
Specifically, the service information is sequentially subjected to constraint registration according to the corresponding server-side host name, the API port name and the name information.
Specifically, the calling and arranging process of the API arranging file is as follows:
and selecting input parameter information, target service end API information, execution sequence information among the target service end API information and the target service end API information corresponding to the target service in the target service end combination from a metadata base through a preset interactive interface, and filling the input parameter information, the target service end API information, the execution sequence information among the target service end API information and the target service end API information into a preset micro-service arrangement template so as to configure and generate a service arrangement file.
Specifically, the output result information includes information processed according to a preset calling result of the arranged server side combination.
Specifically, the processing is performed according to the preset calling result of the arranged server side combination, which comprises at least one of the following steps:
combining scheduling results of the arranged server side combination;
and cutting the scheduling result of the arranged server-side combination.
Specifically, parsing the API orchestration file includes the following steps:
dynamically generating a corresponding abstract object according to the obtained service arrangement file;
generating a service arrangement result according to the abstract object;
acquiring corresponding identification tags and input parameter information in the service arrangement file based on service application information sent by an application terminal;
and calling the server according to the execution sequence between the execution logic of the server API port of the API arrangement file and the target service API port to obtain a corresponding server call list on the basis of the identification tag and the input parameter information.
The application also provides a service arrangement system which is realized by the gateway-based service arrangement method, and comprises an acquisition module, an analysis module, a metadata module, a transmission module, a service arrangement module and a service scheduling module.
The service arrangement module configures the generated service arrangement file based on the service arrangement template, the target service end combination and the logic relation between the target service ends in the target service end combination.
The transmission module is used for data transmission among the modules.
The metadata module is used for storing configuration information and service arrangement files of the target server side;
the acquisition module is used for receiving a plurality of service requests, and each service request is a request message called by an API interface.
The analyzing module is used for analyzing the acquired request message to obtain the identification tag and the input parameter information of the corresponding API interface.
And the service calling module is used for matching the service arrangement files in the metadata module based on the identification tag to obtain corresponding executable scripts.
Executing the executable script through the input parameter information, and calling the target server side API interface contained in the micro-service orchestration file according to the execution logic of the configured target server side API interface in the service orchestration file and the execution sequence information between the target server side API interfaces.
The application also provides a data processing device, which comprises a memory and a processor; wherein the memory is configured to store one or more computer instructions that are executed by the processor to perform the gateway-based service orchestration method described above.
The present application is a computer readable storage medium having stored thereon computer instructions that, when executed, perform the gateway-based service orchestration method described above.
Compared with the prior art, the application has the beneficial effects that:
the application carries out constraint registration on each service end in advance, thereby orderly combining various services to complete a certain function in the actual use process, and a user can realize the call of a plurality of services through one call request.
Drawings
Fig. 1 is a flow chart of a service orchestration method according to the present embodiment;
fig. 2 is a block diagram of a service orchestration system according to the present embodiment;
fig. 3 is a block diagram of a data processing apparatus according to the present embodiment.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments.
All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Before describing the service arrangement method provided by the application, technical terms related to the application are introduced:
API: application Programming Interface, application programming interface.
JSON language: the JSON language is a lightweight data interaction format, and the data is stored and represented by adopting a text format completely independent of a programming language, so that the JSON language is easy to read and write by people, is easy to analyze and generate by machines, and effectively improves the network transmission efficiency.
Service orchestration: one or more services are combined according to certain logic to construct a combination service with coarser granularity, and simultaneously, the services are provided outside in the form of an API.
As shown in fig. 1, a service orchestration method includes:
and S100, exposing and restraining the service information and the API port information provided by each service end to obtain corresponding registration information.
S110, configuring and generating a service arrangement file according to the registration information and the execution sequence between the execution logic of each server side API interface and the server side API interface, wherein the configuration content of the service arrangement file comprises identification information of the service arrangement file, input parameter information, target server side API interface information, the execution logic of the target server side API interface and the execution sequence between the server side API interfaces, and output result information.
S120, constructing a corresponding service arrangement model based on the service arrangement file of the service end;
and analyzing the service arrangement model according to the service request sent by the application end to obtain a corresponding service list.
Further, the specific procedure for S100 is as follows:
and S101, storing the hostname, port and name information required by the service according to the exposed service provided by the service provider into a database corresponding to the metadata module.
S102, according to the exposure API provided by the service provider, parameters, calling modes and name information of the exposure API are stored into a corresponding database through an interface preset by the metadata module.
In the embodiment of the application, the service provider sends the information registration request to the server (the server is a metadata module) through the client (the client can be an APP application or a browser). The server receives an information registration request sent by the client and detects whether the request information meets a preset registration information format.
The specific procedure for S110 is as follows:
and S111, if the service information and the API information meet the preset registration information format, accessing a database corresponding to the visualization system through a preset access interface.
S112, according to a preset service arrangement template, a micro-service arrangement file is configured and generated based on a target service end combination and a logic relation between target service ends in the target service end combination.
S113, storing the configuration generation micro-service arrangement file into a corresponding database through a pre-established interface.
In the embodiment of the application, the configuration content of the service orchestration template comprises: and the identification information, the input parameter information, the target server interface information and the execution sequence information among the target server interface information of the micro-service orchestration file.
In this embodiment, the target server interface may include at least one of the following information: the name of the method, the parameter information and the name of the interface service, so that the information of the interface of the target server to be called can be flexibly configured according to the service requirement.
In this embodiment, the execution sequence information command between the target server interface information may be set in advance in the micro service orchestration template, and the execution logic of the corresponding server interface may be corresponding, so that the execution logic of the target server combination may be set efficiently and flexibly as required.
In order to enable those skilled in the art to better understand and practice the embodiments of the present disclosure, a detailed description is provided below with reference to a specific application scenario.
As shown below, a micro-service orchestration template according to one embodiment of the present disclosure is described in Domain-Specific Language, DSL, language. The specific format is as follows:
in the micro-service orchestration template, various information in the micro-service orchestration template is respectively represented in a JS object numbered musical notation (JavaScript Object Notation, JSON) form.
Wherein: the APIS node is adapted to characterize a set of target server interface information for micro-service orchestration.
The Services node is adapted to characterize the target service interface host information, and in particular implementations may include the host name, port number of the interface. In the micro service orchestration template, the Host name "Host" and the Port number "Port" of the interface are shown, and the Host name and the Port number of the corresponding interface include: "127.0.0.1" and "8080". In a specific configuration process, all target server interfaces in the related server interface combination can be configured.
The Path node is adapted to characterize Path information of the target server interface.
The Protocol node is adapted to characterize a target service interface request Protocol.
The Method node is adapted to characterize the target service interface request mode.
The Parameter node is adapted to characterize the target server interface request Parameter, through which the format of the input parameters of the target server interface can be configured. As shown in the micro-service orchestration template, the Type in the Parameter node is adapted to set the Type required by the corresponding interface for identifying the Parameter placement Type when constructing the request message. As shown in the micro-service orchestration template described above, keys in the Parameter node are adapted to set corresponding interface Parameter positions. As indicated by the micro-service orchestration template described above, defaultValue in the Parameter node is adapted to set that the value of the DefaultValue node is used instead when the corresponding interface node Key does not have corresponding data. As indicated above for the micro-service orchestration template, the requirements in the Parameter node are adapted to set whether the corresponding interface has to Require corresponding parameters. As indicated above for the micro-service orchestration template, the Body node in the Parameter node is adapted to make a request as an input Parameter when the corresponding interface Type node value is Body. It will be appreciated that in implementations, different input parameters may be set depending on the particular type of service.
The Headers node is adapted to characterize the request header of the target server interface, through which the format of the request header of the target server interface can be configured. As shown in the micro-service orchestration template described above, keys in the Headers node are adapted to set the required request header positions for the corresponding interfaces. As shown in the micro-service orchestration template, the DefaultValue in the Headers node is adapted to be replaced with the value of the DefaultValue node when the corresponding interface node Key is set to have no corresponding data. It will be appreciated that in implementations, different numbers of request headers may be set depending on the particular type of service.
The BatchIndex node is adapted to characterize the target service interface request order by which the execution order between target service interfaces can be configured, i.e., by which the orchestration flow can be dynamically generated. As shown in the micro-service orchestration template described above, numbers may be filled in to configure the order of execution of the micro-services.
The Name node is suitable for representing the unique identifier of the target server interface, and the client can acquire corresponding micro-service return information through the identifier. Each target server interface and the combinational logic correspond to the identification of the unique micro-service orchestration file. It will be appreciated that in implementations, different unique identifiers may be set depending on the particular type of service.
The ParentApi node is adapted to characterize the execution logic of the target server interface, through which the execution parameters of the target server interface can be configured. As shown in the micro-service orchestration template, the ParentName node in the ParentApi nodes is adapted to set the last called server interface name. As shown in the micro-service orchestration template, the Key node in the ParentApi node is suitable for setting a specific position of a calling result returned by the last called server interface. As shown in the micro-service orchestration template, the DefaultValue node in the partentapi node is suitable for being filled as a parameter when the last called server interface return does not exist. As shown in the micro-service orchestration template, the key node in the partentapi node is adapted to set the parameter position of the last called server interface return data in the target server interface. As shown in the micro-service orchestration template, the ToType node in the ParentApi node is suitable for setting the parameter type of the last called server interface return data in the target server interface. It will be appreciated that in implementations, different parameters may be set depending on the particular type of service.
The specific procedure for S120 is as follows:
s121, analyzing the micro-service arrangement file generated by configuration, and dynamically generating a preset abstract object.
S122, generating a service orchestration calling result according to the preset abstract object.
S123, responding to a micro-service call request, and acquiring identification information and input parameter information of a micro-service orchestration file corresponding to the micro-service call request.
S124, based on the identification information and the input parameter information, calling the target service end interfaces contained in the preset abstract object according to execution logic of the configuration target service end interfaces in the preset abstract object and execution sequence information between the target service end interfaces.
S125, returning output result information.
In this embodiment, after obtaining the custom DSL statement corresponding to the URL from the database, the DSL statement is first deserialized to generate the preset abstract object. In the embodiment of the application, the preset abstract object comprises request service information, an input path and input parameters.
As shown in fig. 2, this embodiment further provides a service orchestration system, which is implemented based on the service orchestration method provided in the foregoing embodiment, and includes an obtaining module 201, an analyzing module 202, a metadata module 203, a transmitting module 204, a service orchestration module 205, and a service invoking module 206.
The obtaining module 201 is configured to obtain N messages to be forwarded in the received N forwarding requests; each message to be forwarded is a request message called by an interface or a response message called by an interface; wherein N is an integer greater than or equal to 1.
The parsing module 202 is configured to parse each message to be forwarded to obtain detailed information of interface request parameters of an interface called by each message to be forwarded; and the N interface request parameter detailed information is respectively obtained corresponding to the N messages to be forwarded.
The metadata module 203 is configured to store the target service configuration information and the micro service orchestration file.
The transmission module 204 is configured to transmit M pieces of the interface detail definition information to the service orchestration module 205, so that the service orchestration module 205 micro-services the M interfaces based on the M pieces of the interface detail definition information.
The service orchestration module 205 is configured to generate a micro-service orchestration file according to a preset micro-service orchestration template, based on a target micro-service combination and a logic relationship between target micro-services in the target micro-service combination, where configuration content of the micro-service orchestration file includes: the identification information, the input parameter information, the target server interface information, the execution logic of the target server interface and the execution sequence information between the target server interfaces of the micro service orchestration file, and the output result information; analyzing the micro-service orchestration file generated by configuration, and dynamically generating a corresponding executable script; and responding to the micro-service call request, acquiring the identification information and the input parameter information of the micro-service orchestration file corresponding to the micro-service call request, and matching the identification information of the acquired micro-service orchestration file with an executable script corresponding to the identification information of the micro-service orchestration file.
The service calling unit 206 is adapted to execute the executable script based on the input parameter information, and call the target service interfaces included in the micro service orchestration file according to the execution logic of the configured target service interfaces in the micro service orchestration file and the execution sequence information between the target service interfaces.
As shown in fig. 3, a block diagram of a data processing apparatus 300 according to the present embodiment is provided. The data processing apparatus 300 is a server, and the server may be an independent server or a server cluster formed by a plurality of servers.
The data processing device 300 comprises a processor 302, a memory and a network interface 305 connected by a system bus 301, wherein the memory may comprise a storage medium 303 and an internal memory 304.
The storage medium 303 may store an operating system 3031 and a computer program 3032. The computer program 3032, when executed, may cause the processor 302 to perform a service orchestration call method.
The processor 302 is used to provide computing and control capabilities to support the operation of the overall computer device 300.
The internal memory 304 provides an environment for the execution of a computer program 3032 in the storage medium 303, which computer program 3032, when executed by the processor 302, causes the processor 302 to perform a service orchestration call method.
The network interface 305 is used for network communication with other devices. It will be appreciated by those skilled in the art that the block diagrams of the partial structures associated with the aspects of the application are not limiting of the computer device 300 to which the aspects of the application may be applied, and that a particular computer device 300 may include more or less elements than those shown, or may be combined with certain elements, or may have different arrangements of elements.
Wherein the processor 302 is configured to execute a computer program 3032 stored in a memory to implement the following steps: if a URL service arrangement calling request sent by a client is received, identification information and input parameter information of a micro service arrangement file corresponding to the URL service arrangement calling request are obtained. And calling the target micro-service interface contained in the preset abstract object according to the execution logic of the configured target micro-service interface in the preset abstract object and the execution sequence information between the target micro-service interfaces based on the identification information and the input parameter information. And sending the service orchestration calling result to the client.
It should be appreciated that in this embodiment, the processor 302 may be a central processing unit (Central Processing Unit, CPU), the processor 302 may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf Programmable gate arrays (FPGAs) or other Programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. Wherein the general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
Claims (10)
1. A gateway-based service orchestration method for associating a plurality of service ends and application ends, the service orchestration method comprising the steps of:
exposing and restricting service information and API port information provided by each service end to obtain corresponding registration information;
according to the registration information and the execution sequence between the execution logic of each server side API interface and the server side API interface, configuring and generating a service arrangement file, wherein the configuration content of the service arrangement file comprises identification information of the service arrangement file, input parameter information, target server side API interface information, the execution logic of the target server side API interface and the execution sequence between the server side API interfaces, and output result information;
constructing a corresponding service arrangement model based on the service arrangement file of the service end;
and analyzing the service arrangement model according to the service request sent by the application end to obtain a corresponding service list.
2. The gateway-based service orchestration method according to claim 1, wherein the API port information is constraint registered sequentially according to parameters, calling mode, and name information order.
3. The gateway-based service orchestration method according to claim 1, wherein the service information is constraint registered sequentially according to the corresponding server-side host name, API port name, and name information.
4. The gateway-based service orchestration method according to claim 1, wherein the calling and orchestration process of the API orchestration file is as follows:
and selecting input parameter information, target service end API information, execution sequence information among the target service end API information and the target service end API information corresponding to the target service in the target service end combination from a metadata base through a preset interactive interface, and filling the input parameter information, the target service end API information, the execution sequence information among the target service end API information and the target service end API information into a preset micro-service arrangement template so as to configure and generate a service arrangement file.
5. The gateway-based service orchestration method according to claim 1, wherein the output result information contains information that is processed according to call results of preset orchestration of service side combinations.
6. The gateway-based service orchestration method according to claim 5, wherein the processing according to the call results of the preset orchestration of service side combinations comprises at least one of:
combining scheduling results of the arranged server side combination;
and cutting the scheduling result of the arranged server-side combination.
7. The gateway-based service orchestration method according to claim 1, wherein parsing the API orchestration file comprises the steps of:
dynamically generating a corresponding abstract object according to the obtained service arrangement file;
generating a service arrangement result according to the abstract object;
acquiring corresponding identification tags and input parameter information in the service arrangement file based on service application information sent by an application terminal;
and calling the server according to the execution sequence between the execution logic of the server API port of the API arrangement file and the target service API port to obtain a corresponding server call list on the basis of the identification tag and the input parameter information.
8. A service orchestration system, characterized in that it is implemented by a gateway-based service orchestration method according to any one of claims 1-7, comprising an acquisition module, an parsing module, a metadata module, a transmission module, a service orchestration module, and a service scheduling module;
the service arrangement module is used for configuring the generated service arrangement file based on the service arrangement template, the target service end combination and the logic relation between the target service ends in the target service end combination;
the transmission module is used for data transmission among the modules;
the metadata module is used for storing configuration information and service arrangement files of the target server side;
the acquisition module is used for receiving a plurality of service requests, and each service request is a request message called by an API interface;
the analyzing module is used for analyzing the acquired request message to acquire an identification tag and input parameter information of a corresponding API interface;
the service calling module is used for matching the service arrangement files in the metadata module based on the identification tag to obtain corresponding executable scripts;
executing the executable script through the input parameter information, and calling the target server side API interface contained in the micro-service orchestration file according to the execution logic of the configured target server side API interface in the service orchestration file and the execution sequence information between the target server side API interfaces.
9. A data processing apparatus comprising a memory and a processor; wherein the memory is for storing one or more computer instructions for execution by the processor of the gateway-based service orchestration method according to any one of claims 1-7.
10. A computer readable storage medium having stored thereon computer instructions, which when run perform the gateway-based service orchestration method according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310496267.3A CN116668520A (en) | 2023-05-05 | 2023-05-05 | Gateway-based service arrangement method, system, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310496267.3A CN116668520A (en) | 2023-05-05 | 2023-05-05 | Gateway-based service arrangement method, system, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116668520A true CN116668520A (en) | 2023-08-29 |
Family
ID=87708846
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310496267.3A Pending CN116668520A (en) | 2023-05-05 | 2023-05-05 | Gateway-based service arrangement method, system, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116668520A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117369784A (en) * | 2023-12-06 | 2024-01-09 | 之江实验室 | Processing system and method of service interface |
-
2023
- 2023-05-05 CN CN202310496267.3A patent/CN116668520A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117369784A (en) * | 2023-12-06 | 2024-01-09 | 之江实验室 | Processing system and method of service interface |
| CN117369784B (en) * | 2023-12-06 | 2024-03-05 | 之江实验室 | Processing system and method of service interface |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6912469B2 (en) | Access request conversion method and device | |
| CN110198247B (en) | Interface test method and system | |
| US11716264B2 (en) | In situ triggered function as a service within a service mesh | |
| CN112306881B (en) | Analog data generation method, device, equipment and storage medium | |
| WO2021073202A1 (en) | Intelligent contract processing method, computer device and storage medium | |
| US11115913B2 (en) | Wireless communication core network and method for analyzing user equipment mobility in the same | |
| CN112732572A (en) | Service testing method, device and system, storage medium and electronic device | |
| CN111988418B (en) | Data processing method, device, equipment and computer readable storage medium | |
| CN109104368B (en) | Connection request method, device, server and computer readable storage medium | |
| CN116668520A (en) | Gateway-based service arrangement method, system, equipment and storage medium | |
| CN111367685A (en) | Interface calling method and device, computer equipment and storage medium | |
| CN113179269B (en) | Protocol data analysis method, system and medium based on Internet of things | |
| CN114025027A (en) | Data transmission script running method and device, storage medium and electronic device | |
| CN115509647B (en) | API (application program interface) access method, conversion method, device, equipment and storage medium | |
| CN111414154A (en) | Method and device for front-end development, electronic equipment and storage medium | |
| CN116233217A (en) | Page jump method and device based on route, electronic equipment and storage medium | |
| CN115374207A (en) | Service processing method and device, electronic equipment and computer readable storage medium | |
| US9537931B2 (en) | Dynamic object oriented remote instantiation | |
| CN115454878A (en) | Interface calling test method applied to micro service and related device | |
| CN114675821A (en) | Service standardization system and method based on low codes | |
| CN113691618A (en) | Message notification method, device, message center and storage medium | |
| JP2022542203A (en) | Mini-program batch processing method, device, electronic device and readable storage medium | |
| CN112000313A (en) | Request response method, device, equipment and storage medium | |
| CN112637288A (en) | Streaming data distribution method and system | |
| CN112217852A (en) | Platform-as-a-service system and method based on workflow engine |
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 |