CN112199079B - System docking method, computing device and storage medium - Google Patents
System docking method, computing device and storage medium Download PDFInfo
- Publication number
- CN112199079B CN112199079B CN202011413243.XA CN202011413243A CN112199079B CN 112199079 B CN112199079 B CN 112199079B CN 202011413243 A CN202011413243 A CN 202011413243A CN 112199079 B CN112199079 B CN 112199079B
- Authority
- CN
- China
- Prior art keywords
- service request
- service
- response
- standard interface
- determining
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/22—Procedural
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The present disclosure relates to a system interfacing method, a computing device, and a storage medium. The method comprises the following steps: in response to receiving a service request from a client system, acquiring a client identifier and a service type indicated in the service request; based on the service type, forwarding the service request to a corresponding service flow interface; determining whether the service request conforms to a standard interface definition based on the client identifier; in response to determining that the service request conforms to the standard interface definition, processing the service request according to a standard service flow; in response to determining that the service request does not conform to the standard interface definition, extracting parameters of the service data in the service request to generate a parameter extraction object; and converting the parameter extraction object into an analysis result object through domain specific language conversion so as to process the service request based on the analysis result object, wherein the analysis result object conforms to the standard interface definition. The method and the system can realize system docking between systems with different interface definitions, so as to be beneficial to shortening development period and reducing development cost.
Description
Technical Field
Embodiments of the present disclosure generally relate to the field of system docking, and in particular, to a system docking method, a computing device, and a storage medium.
Background
With the rapid development of the internet, data sharing through system docking becomes more and more frequent. Conventional system interfacing requires that the two systems interfacing agree on an interface standard. Generally, one system develops a set of standard interface definitions in advance and declares the standard interface definitions to another system; and the other system develops or modifies a program according to the standard interface definition to carry out system matching so as to realize the call to the interface.
However, when interfacing with a plurality of different systems, it is necessary to develop or modify a program in each system to be accessed according to standard interface definitions, which greatly extends the development period and increases the development cost. Therefore, the conventional system docking method has the defects of high development cost, low development efficiency and the like.
Disclosure of Invention
The present disclosure provides a system docking method, a computing device, and a storage medium, which can implement system docking between systems having different interface definitions, so as to facilitate shortening a development period and reducing development costs.
According to a first aspect of the present disclosure, a system docking method is provided. The method comprises the following steps: in response to receiving a service request from a client system, acquiring a client identifier and a service type indicated in the service request; based on the service type, forwarding the service request to a corresponding service flow interface; determining whether the service request conforms to a standard interface definition based on the client identifier; in response to determining that the service request conforms to the standard interface definition, processing the service request according to a standard service flow; in response to determining that the service request does not conform to the standard interface definition, extracting parameters of the service data in the service request to generate a parameter extraction object; and converting the parameter extraction object into a parsing result object through a Domain Specific Language (DSL) conversion so as to process the service request based on the parsing result object, wherein the parsing result object conforms to the standard interface definition.
According to a second aspect of the present disclosure, a computing device is also provided. The computing device includes: at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions when executed by the at least one processing unit, cause the computing device to perform the method of the first aspect of the disclosure.
According to a third aspect of the present disclosure, there is also provided a computer-readable storage medium. The computer readable storage medium has stored thereon a computer program which, when executed by a machine, performs the method of the first aspect of the disclosure.
In some embodiments, the domain-specific language conversion includes at least any one of the following operations: in response to determining that the parameter extraction object includes an initial mapping field for a mapping operation, generating a mapping operation designator to perform a corresponding field mapping operation using a preconfigured parser corresponding to the client system to map the initial mapping field to a mapping result field; in response to determining that the parameter extraction object includes an initial replacement field for a default value replacement operation, generating a replacement operation designator to perform, with the parser, a corresponding default value replacement operation to replace the corresponding parameter value of the initial replacement field with a predetermined default value; or in response to determining that the parameter extraction object includes an initial hidden field for a hiding operation, generating a hidden operation designator to perform, with the parser, the corresponding field hiding operation to hide the initial hidden field; wherein the initial mapped field, the initial replacement field, and the initial hidden field are included in a preconfigured database of fields corresponding to the client system.
In some embodiments, the system docking method further comprises: responding to a service request received from a client system, distributing the service request to a server physical resource corresponding to the client system according to a client identifier, and controlling the flow rate of the service request not to exceed a preset flow rate threshold value by the server physical resource through a token bucket algorithm.
In some embodiments, extracting the parameters of the service data in the service request comprises: determining whether the data format of the service data is a Json format or not based on the service request; if the data format is the Json format, acquiring a parameter extraction object in the Json format based on the service data; if the data format is other than the Json format, the input parameters in other formats are obtained based on the service data, so that the input parameters in other formats are converted into parameter extraction objects in the Json format.
In some embodiments, the parameter extraction object conforms to a predetermined parameter definition, wherein processing the service request based on the parsing result object comprises: executing corresponding business operation processing based on the analysis result object; integrating the processing results of the corresponding business operation processing, wherein the processing results conform to the standard interface definition; converting the processing result into an output parameter which is defined according to a preset parameter by utilizing a pre-configured resolver corresponding to the client system; and sending the output parameters to the client system.
In some embodiments, the traffic type comprises any one of: commodity services, order services, or after-market services.
In some embodiments, the system docking method further comprises: in response to receiving a service request at a service flow interface, intercepting the service request by an interceptor; and based on the client identification, the service request is authenticated through the authentication module so as to verify the access authority of the client system to the service flow interface.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Like or corresponding reference characters designate like or corresponding parts throughout the several views.
Fig. 1 shows a schematic diagram of a system for implementing a system docking method according to an embodiment of the present disclosure.
Fig. 2 shows a flow chart of a system docking method according to an embodiment of the present disclosure.
Fig. 3 shows a flow chart of a method for extracting parameters of service data in a service request according to an embodiment of the disclosure.
FIG. 4 shows a flow diagram of a method for processing a service request based on a parsing result object according to an embodiment of the disclosure.
Fig. 5 schematically shows a schematic diagram of a method for flow control according to an embodiment of the present disclosure.
Fig. 6 schematically shows a schematic diagram of a system for processing a service request according to an embodiment of the present disclosure.
FIG. 7 schematically shows a block diagram of an electronic device suitable for use to implement embodiments of the present disclosure.
Detailed Description
Preferred embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the preferred embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
The term "include" and variations thereof as used herein is meant to be inclusive in an open-ended manner, i.e., "including but not limited to". Unless specifically stated otherwise, the term "or" means "and/or". The term "based on" means "based at least in part on". The terms "one example embodiment" and "one embodiment" mean "at least one example embodiment". The term "another embodiment" means "at least one additional embodiment". The terms "first," "second," and the like may refer to different or the same object.
As described above, in the conventional system docking method, when there are a plurality of different systems to be docked, a program needs to be developed or modified in each system to be accessed according to the standard interface definition. Therefore, the conventional system docking method has the defects of high development cost, low development efficiency and the like.
To address, at least in part, one or more of the above problems, and other potential problems, example embodiments of the present disclosure set forth a system docking method. The method comprises the following steps: in response to receiving a service request from a client system, acquiring a client identifier and a service type indicated in the service request; based on the service type, forwarding the service request to a corresponding service flow interface; determining whether the service request conforms to a standard interface definition based on the client identifier; in response to determining that the service request conforms to the standard interface definition, processing the service request according to a standard service flow; in response to determining that the service request does not conform to the standard interface definition, extracting parameters of the service data in the service request to generate a parameter extraction object; and converting the parameter extraction object into an analysis result object through domain specific language conversion so as to process the service request based on the analysis result object, wherein the analysis result object conforms to the standard interface definition.
In the above scheme, the present disclosure can extract parameters of service data in a service request for systems with different interface definitions to generate a parameter extraction object, without developing or modifying a program in each system to be accessed according to a standard interface definition developed in advance; and converting the parameter extraction object into an analysis result object through domain specific language conversion so as to process the service request based on the analysis result object, wherein the analysis result object conforms to the standard interface definition. Compared with the traditional system docking method, the system docking method can realize system docking between systems with different interface definitions, and programs do not need to be developed or modified in each system to be accessed according to the standard interface definition developed in advance, so that the development period can be greatly shortened, and the development cost can be reduced. Therefore, the present disclosure can shorten the development period required to implement system docking and reduce development costs.
Fig. 1 shows a schematic diagram of a system 100 for implementing a system docking method according to an embodiment of the present disclosure. As shown in fig. 1, the system 100 includes: a request receiving unit 112, a request forwarding unit 114, a standard interface determining unit 116, a request processing unit 118, a parameter extracting unit 120 and a DSL converting unit 122. In some embodiments, the system 100 may also include a server 140 and a network 150. System 100 may also include client system(s) 160.
In some embodiments, the request receiving unit 112, the request forwarding unit 114, the standard interface determining unit 116, the request processing unit 118, the parameter extraction unit 120, and the DSL conversion unit 122 may be configured on one or more computing devices 130. Computing device 130 may interact data with server 140 via wired or wireless means (e.g., network 150), and computing device 130 may interact data with client system(s) 160 via network 150.
With respect to the computing device 130, it is used to receive service requests from client systems and to process the service requests. The service request may be a service request conforming to the standard interface definition or a service request not conforming to the standard interface definition. The type of service requested by the service is, for example and without limitation, a commodity service, an order service, or an after-market service.
With respect to receiving a service request from a client system, the computing device 130 is specifically configured to determine whether the service request complies with the standard interface definition based on the client identification indicated in the service request.
With respect to processing the service request, if it is determined that the service request conforms to the standard interface definition, the computing device 130 is configured to process the service request according to a standard service flow; if the service request is determined not to conform to the standard interface definition, the computing device 130 is configured to extract parameters of the service data in the service request to generate a parameter extraction object, and convert the parameter extraction object into a parsing result object conforming to the standard interface definition through DSL conversion to process the service request based on the parsing result object.
In some embodiments, computing device 130 may have one or more processing units, including special purpose processing units such as GPUs, FPGAs, ASICs, and general purpose processing units such as CPUs. In addition, one or more virtual machines may also be running on each computing device.
With respect to the request receiving unit 112, it is used to receive service requests from client systems. For example, request receiving unit 112 may obtain a service request from client system 160 via network 150. The service request is, for example, a commodity service request, an order service request, or an after-market service request.
Regarding the request forwarding unit 114, it is used to forward the service request to the corresponding service flow interface based on the service type indicated in the service request. For example, request forwarding unit 114 may forward the goods service request to a goods service interface, or forward the order service request to an order service interface, or forward the after-market service request to an after-market service interface.
A standard interface determination unit 116 is used for determining whether the service request complies with the standard interface definition based on the client identification indicated in the service request.
With respect to the request processing unit 118, it is used to process service requests. If the service request is determined to conform to the standard interface definition, the request processing unit 118 processes the service request according to a standard service flow.
And a parameter extracting unit 120, configured to, in response to determining that the service request does not conform to the standard interface definition, extract a parameter of the service data in the service request to generate a parameter extraction object, which conforms to a predetermined parameter definition. In one embodiment, extracting the parameters of the service data in the service request comprises: determining whether the data format of the service data is a Json format or not based on the service request; if the data format is the Json format, acquiring a parameter extraction object in the Json format based on the service data; if the data format is other than the Json format, the input parameters in other formats are obtained based on the service data, so that the input parameters in other formats are converted into parameter extraction objects in the Json format.
With respect to the DSL conversion unit 122, it is used to convert the parameter extraction object into a parsing result object conforming to the standard interface definition through DSL conversion, so as to process the service request by the request processing unit 118 based on the parsing result object.
A system docking method 200 according to an embodiment of the present disclosure will be described below in conjunction with fig. 2. Fig. 2 shows a flow diagram of a system docking method 200 according to an embodiment of the present disclosure. It should be understood that the method 200 may be performed, for example, at the electronic device 700 depicted in fig. 7. May also be executed at the computing device 130 depicted in fig. 1. It should be understood that method 200 may also include additional acts not shown and/or may omit acts shown, as the scope of the disclosure is not limited in this respect.
At step 202, computing device 130 may obtain, in response to receiving a service request from a client system, a client identification and a service type indicated in the service request. In the field of electronic commerce, types of business include, but are not limited to, commodity services, order services, or after-market services. The client identification corresponds to a client system for identifying the client system.
At step 204, the computing device 130 may forward the service request to the corresponding service flow interface based on the service type.
In one embodiment, the computing device 130 may intercept, via an interceptor, a business request in response to receiving the business request at a business process interface; and based on the client identification, the service request is authenticated through the authentication module so as to verify the access authority of the client system to the service flow interface.
At step 206, the computing device 130 may determine whether the service request conforms to the standard interface definition based on the customer identification.
If the service request is determined to conform to the standard interface definition at step 206, i.e., "yes," then proceeding to step 208, the computing device 130 may process the service request according to a standard business process.
If it is determined at step 206 that the service request does not conform to the standard interface definition, i.e., "no," then proceeding to step 210, the computing device 130 may extract parameters of the service data in the service request to generate a parameter extraction object.
At step 212, the computing device 130 may convert the parameter extraction object to a parsing result object via DSL conversion in order to process the service request based on the parsing result object, the parsing result object conforming to the standard interface definition.
In one embodiment, the computing device 130 may generate a mapping operation designator to perform a corresponding field mapping operation using a preconfigured parser corresponding to the client system to map the initial mapping field to the mapping result field in response to determining that the parameter extraction object includes an initial mapping field for the mapping operation.
In one embodiment, the computing device 130 may generate a replacement operation designator to perform, with the parser, a corresponding default value replacement operation to replace the corresponding parameter value of the initial replacement field with a predetermined default value in response to determining that the parameter extraction object includes an initial replacement field for the default value replacement operation.
In one embodiment, the computing device 130 may generate the hidden operation instructor to perform a corresponding field hiding operation with the parser to hide the initial hidden field in response to determining that the parameter extraction object includes the initial hidden field for the hiding operation.
In one embodiment, the initial mapped field, the initial replacement field, and the initial hidden field are included in a preconfigured database of fields corresponding to the client system. The computing device 130 generates a parsing result object that conforms to the standard interface definition by performing a corresponding field operation with the parser in response to determining that the parameter extraction object includes a field in the field database.
In the above solution, the parsing result object conforming to the standard interface definition can be generated based on the service request not conforming to the standard interface definition, so as to be used for processing the service request. The system interface can be realized between systems with different interface definitions, and programs do not need to be developed or modified in each system to be accessed according to the standard interface definition developed in advance, so that the development period can be greatly shortened, and the development cost can be reduced.
A method 300 for extracting parameters of service data in a service request according to an embodiment of the present disclosure will be described below in conjunction with fig. 3. Fig. 3 shows a flow diagram of a method 300 for determining path directions for a business process in accordance with an embodiment of the present disclosure. It should be understood that the method 300 may be performed, for example, at the electronic device 700 depicted in fig. 7, and may also be performed at the computing device 130 depicted in fig. 1. It should be understood that method 300 may also include additional acts not shown and/or may omit acts shown, as the scope of the disclosure is not limited in this respect.
At step 302, the computing device 130 may determine whether the data format of the business data is a Json format based on the business request. In one embodiment, the computing device 130 may determine whether the data format of the service data is in a Json format based on the client identification of the service request.
If it is determined at step 302 that the data format of the business data is in Json format, i.e., "yes," then proceeding to step 304, the computing device 130 may obtain a parameter extraction object in Json format based on the business data.
If it is determined at step 302 that the data format of the business data is not in the Json format, i.e., "no," then proceeding to step 306, the computing device 130 may obtain input parameters in other formats based on the business data to convert the input parameters in other formats to parameter extraction objects in the Json format. In one embodiment, the parameter extraction object conforms to a predetermined parameter definition.
In one embodiment, the data transmission may be performed by using an http interface, and the data format may be a Json format or other formats. It should be noted that the data format is not limited to the Json format, but may also be other data formats, such as form format or text/play text format. The computing device 130 may determine a data format of the service request from the client system based on a client identification corresponding to the client system; and extracting parameters in the service data according to the data format, and converting the parameters into parameter extraction objects in a Json format through a Jackson tool. For example, in one embodiment, the computing device 130 determines that the data format of the client system is in form format based on the client identification; extracting map data from the business data in the form format; and converting the acquired map data into a Json format through a Jackson tool, thereby obtaining a parameter extraction object in the Json format.
In one embodiment, the computing device 130 may intercept the traffic request through an interceptor; determining a body type of the service request according to the content type in the header of the service request; and encapsulating the service request according to the body type of the service request. The computing device 130 may determine, based on the encapsulated service request, whether the service request conforms to the standard interface definition; in response to determining that the service request conforms to the standard interface definition, processing the service request according to a standard service flow; in response to determining that the service request does not conform to the standard interface definition, a parsing result object conforming to the standard interface definition is generated for processing the service request by parameter extraction and DSL conversion.
In one embodiment, the computing device 130 obtains the encapsulated service request in response to determining that the service request does not conform to the standard interface definition; determining the content type of the service request; extracting parameters in the body according to the content type; and converting the parameters into parameter extraction objects in a Json format through a Jackson tool.
A method 400 for processing a service request based on a parsing result object according to an embodiment of the present disclosure will be described below in conjunction with fig. 4. Fig. 4 shows a flowchart of a method 400 for determining a path run of a business process, in accordance with an embodiment of the present disclosure. It should be understood that method 400 may be performed, for example, at electronic device 700 depicted in fig. 7, and may also be performed at computing device 130 depicted in fig. 1. It should be understood that method 400 may also include additional acts not shown and/or may omit acts shown, as the scope of the disclosure is not limited in this respect.
At step 402, the computing device 130 may perform a corresponding business operation process based on the parsed result object. In one embodiment, when the business type is commodity service, the computing device 130 may perform the following operations based on the parsing result object: parameter checking, commodity data acquisition and picture information acquisition. In one embodiment, when the business type is order service, the computing device 130 may perform the following operations based on the parsing result object: parameter checking and order pushing.
At step 404, the computing device 130 may integrate the processing results of the respective business operation processes, the processing results conforming to the standard interface definition.
At step 406, computing device 130 may convert the processing results into output parameters that conform to the predetermined parameter definitions using a preconfigured parser corresponding to the client system.
At step 408, the computing device 130 may send the output parameters to the client system.
In one embodiment, the computing device 130 may also collect procedural errors during authentication and corresponding business operations processing.
A method 500 for flow control according to an embodiment of the present disclosure will be described below in conjunction with fig. 5. Fig. 5 shows a flow diagram of a method 500 for flow control according to an embodiment of the present disclosure. It should be understood that the method 500 may be performed, for example, at the electronic device 700 depicted in fig. 7, and may also be performed at the computing device 130 depicted in fig. 1. It should be understood that method 500 may also include additional acts not shown and/or may omit acts shown, as the scope of the disclosure is not limited in this respect.
In one embodiment, the computing device 130 may, in response to receiving the service request from the client system, split the service request to a server physical resource corresponding to the client system according to the client identifier, where the server physical resource controls the traffic rate of the service request not to exceed a preset traffic rate threshold through a token bucket algorithm. In one embodiment, the computing device 130, in response to receiving a traffic request from a client system, shunts the traffic request to the corresponding client cluster through the domain name path forwarding service. In one embodiment, the computing device 130 may perform interface-level flow control on the service request through a token bucket algorithm when performing an authentication operation on the service request. For example, the traffic rate threshold for the customer cluster corresponding to the a customer may be set to 100 times/second. When the traffic of the service request exceeds the traffic rate threshold, the computing device 130 returns a programmatic error to the error collector.
By adopting the above means, the present disclosure can perform flow control on the service request from the client system to avoid resource congestion.
A system 600 for processing service requests according to an embodiment of the present disclosure will be described below in conjunction with fig. 6. Fig. 6 schematically shows a schematic diagram of a system 600 for processing a service request according to an embodiment of the present disclosure. It should be understood that method 600 may be performed, for example, at electronic device 700 depicted in fig. 7, and may also be performed at computing device 130 depicted in fig. 1. It should be understood that method 600 may also include additional acts not shown and/or may omit acts shown, as the scope of the disclosure is not limited in this respect.
The configuration model corresponding to the client system is stored in the database of system 600. In one embodiment, the system 600 may, in response to receiving a request from a client system, obtain a client identification and a service type indicated in the service request and forward the service request to a corresponding service flow interface. The system 600 may authenticate the service request based on the client identification to verify the access rights of the client system to the service flow interface. In one embodiment, system 600 may flow control a service request. In response to determining that the client system does not have access to the business process interface, or in response to the traffic of the business request exceeding a traffic rate threshold, the system 600 can return a procedural error to the error collector.
When the service request is determined to conform to the standard interface definition based on the client identification, the system 600 may process the service request according to the standard service flow. For example, when the business type is commodity service, the system 600 may establish a standard commodity service process, and obtain an integrated commodity service processing result through a pipeline model. For example, when the business type is order service, the system 600 may establish a standard order service flow, and obtain an integrated order service processing result through a pipeline model.
When the service request is determined to be not in accordance with the standard interface definition according to the client identifier, the system 600 may generate a parameter extraction object in a Json format through parameter extraction, where the parameter extraction object is in accordance with a predetermined parameter definition; and generating a parsing result object conforming to the standard interface definition through DSL conversion. The system 600 may perform corresponding business operations processing based on the parsed result object; integrating the processing results of the corresponding business operation processing, wherein the processing results conform to the standard interface definition; converting the processing result into an output parameter which is defined according to a preset parameter through DSL conversion; and sending the output parameters to the client system.
In one embodiment, system 600 receives a business request for a commodity service type from an A customer. The client identification indicates that the service request from the a-client does not conform to the standard interface definition. In one embodiment, the system 600 may extract a parameter extraction object from the service request from the a-client that conforms to a predetermined parameter definition, the parameter extraction object including the following fields: "trade name", "commodity price", "stock amount", and "sales amount". These fields are stored in a preconfigured field database corresponding to the a-customer. The system 600 maps "trade name" to "name", maps "commodity price" to "price", maps "stock quantity" to "stock quantity", replaces the corresponding value of "stock quantity" with a predetermined default value (i.e., virtual stock quantity, for example, 999), and hides the "sales volume" field according to a pre-configured resolver corresponding to a customer a through DSL conversion, thereby obtaining a resolution result object that conforms to the standard interface definition. The system 600 performs corresponding business operation processing based on the analysis result object, and obtains a processing result conforming to the standard interface definition. The system 600 maps the "name" in the processing result to the "trade name" and the "price" to the "commodity price" and maps the "stock amount" to the "stock amount" by DSL conversion according to a pre-configured resolver corresponding to the a customer, thereby obtaining an output parameter that meets the definition of the predetermined parameter, and transmits the output parameter to the a customer.
In another embodiment, system 600 receives a business request for a commodity service type from a B-customer. The client identification indicates that the service request from the B-client does not comply with the standard interface definition. In one embodiment, the system 600 may extract a parameter extraction object from the service request from the B-client that conforms to a predetermined parameter definition, the parameter extraction object including the following fields: "commodity name", "price", and "remaining stock quantity". These fields are stored in a preconfigured database of fields corresponding to the B-clients. The system 600 maps the "commodity name" to the "name", the "commodity price" to the "price", and the "remaining stock" to the "stock" through DSL conversion according to a pre-configured resolver corresponding to the B customer, thereby obtaining a resolution result object that conforms to the standard interface definition. The system 600 performs corresponding business operation processing based on the analysis result object, and obtains a processing result conforming to the standard interface definition. The system 600 maps the "name" in the processing result to the "commodity name", maps the "price" to the "price", and maps the "stock amount" to the "remaining stock amount", which is the true remaining stock amount, according to a pre-configured resolver corresponding to the B client through DSL conversion, thereby obtaining an output parameter that conforms to the definition of the predetermined parameter, and transmits the output parameter to the B client.
By adopting the means, the dynamic release of the business services of different clients can be realized by utilizing the pre-configured resolver corresponding to the client system.
FIG. 7 schematically illustrates a block diagram of an electronic device (or computing device) 700 suitable for use to implement embodiments of the present disclosure. The apparatus 700 may be an apparatus for implementing the methods 100 to 600 shown in fig. 2, 4 to 6. As shown in fig. 7, device 700 includes a Central Processing Unit (CPU) 701 that may perform various appropriate actions and processes in accordance with computer program instructions stored in a Read Only Memory (ROM) 702 or computer program instructions loaded from a storage unit 708 into a Random Access Memory (RAM) 703. In the RAM, various programs and data required for the operation of the device 700 may also be stored. The CPU, ROM, and RAM are connected to each other by a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
Various components in the device 700 are connected to the I/O interface 705, including: the input unit 706, the output unit 707, the storage unit 708, the central processing unit 701 performs the various methods and processes described above, such as performing the methods 100-600-for example, in some embodiments, the methods 100-600 may be implemented as a computer software program stored on a machine-readable medium, such as the storage unit 708. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 700 via ROM and/or communications unit 709. When loaded into RAM and executed by a CPU, the computer program may perform one or more of the operations of the methods 100 to 600 described above. Alternatively, in other embodiments, the CPU may be configured by any other suitable means (e.g., by way of firmware) to perform one or more acts of the methods 100-600.
It should be further appreciated that the present disclosure may be embodied as methods, apparatus, systems, and/or computer program products. The computer program product may include a computer-readable storage medium having computer-readable program instructions embodied thereon for carrying out various aspects of the present disclosure.
The computer readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a Static Random Access Memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, a mechanical coding device, such as punch cards or in-groove projection structures having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or electrical signals transmitted through electrical wires.
The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing/processing device, or to an external computer or external storage device via a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing/processing device.
The computer program instructions for carrying out operations of the present disclosure may be assembler instructions, Instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, the electronic circuitry that can execute the computer-readable program instructions implements aspects of the present disclosure by utilizing the state information of the computer-readable program instructions to personalize the electronic circuitry, such as a programmable logic circuit, a Field Programmable Gate Array (FPGA), or a Programmable Logic Array (PLA).
Various aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.
These computer-readable program instructions may be provided to a processor in a voice interaction device, a processing unit of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable medium storing the instructions comprises an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Having described embodiments of the present disclosure, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen in order to best explain the principles of the embodiments, the practical application, or improvements made to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
The above are merely alternative embodiments of the present disclosure and are not intended to limit the present disclosure, which may be modified and varied by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present disclosure should be included in the protection scope of the present disclosure.
Claims (8)
1. A system docking method, comprising:
in response to receiving a service request from a client system, determining whether the service request conforms to a standard interface definition;
in response to determining that the service request conforms to the standard interface definition, processing the service request according to a standard service flow;
in response to determining that the service request does not conform to the standard interface definition, determining, based on the service request, whether a data format of service data in the service request is a Json format;
in response to determining that the data format is a Json format, obtaining a parameter extraction object in the Json format based on the service data;
in response to determining that the data format is other than the Json format, obtaining input parameters of the other format based on the service data so as to convert the input parameters of the other format into parameter extraction objects of the Json format; and
converting the parameter extraction object into a parsing result object through domain specific language conversion so as to process the service request based on the parsing result object, the parsing result object conforming to the standard interface definition,
wherein the domain-specific language translation includes at least any one of:
in response to determining that the parameter extraction object includes an initial mapping field for a mapping operation, generating a mapping operation designator to perform a corresponding field mapping operation using a preconfigured parser corresponding to the client system to map the initial mapping field to a mapping result field;
in response to determining that the parameter extraction object includes an initial replacement field for a default value replacement operation, generating a replacement operation designator to perform, with the parser, a corresponding default value replacement operation to replace a corresponding parameter value of the initial replacement field with a predetermined default value; or
In response to determining that the parameter extraction object includes an initial hidden field for a hiding operation, generating a hidden operation designator to perform, with the parser, a corresponding field hiding operation to hide the initial hidden field;
wherein the initial mapped field, the initial replacement field, and the initial hidden field are included in a preconfigured field database corresponding to the client system.
2. The system docking method of claim 1, wherein determining whether the service request conforms to a standard interface definition comprises:
in response to receiving the service request from the client system, obtaining a client identifier and a service type indicated in the service request;
based on the service type, forwarding the service request to a corresponding service flow interface;
determining whether the service request conforms to the standard interface definition based on the customer identification.
3. The system docking method of claim 2, further comprising:
responding to the received service request from the client system, shunting the service request to a server physical resource corresponding to the client system according to the client identification, wherein the server physical resource controls the flow rate of the service request not to exceed a preset flow rate threshold value through a token bucket algorithm.
4. The system docking method of claim 1, the parameter extraction object conforming to a predetermined parameter definition, wherein processing the service request based on the parsing result object comprises:
executing corresponding business operation processing based on the analysis result object;
integrating the processing results of corresponding business operation processing, wherein the processing results conform to the standard interface definition;
converting the processing result into an output parameter which is defined by the preset parameter by utilizing a pre-configured resolver corresponding to the client system; and
sending the output parameters to the client system.
5. The system docking method of claim 2, wherein the traffic type comprises any one of: commodity services, order services, or after-market services.
6. The system docking method of claim 2, further comprising:
in response to receiving the service request at the service flow interface, intercepting the service request by an interceptor;
and based on the client identification, authenticating the service request through an authentication module so as to verify the access authority of the client system to the service flow interface.
7. A computing device, comprising:
at least one processing unit; and
at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions when executed by the at least one processing unit, cause the apparatus to perform the system docking method of any of claims 1 to 6.
8. A computer-readable storage medium having stored thereon a computer program which, when executed by a machine, implements the system docking method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011413243.XA CN112199079B (en) | 2020-12-07 | 2020-12-07 | System docking method, computing device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011413243.XA CN112199079B (en) | 2020-12-07 | 2020-12-07 | System docking method, computing device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112199079A CN112199079A (en) | 2021-01-08 |
| CN112199079B true CN112199079B (en) | 2021-03-05 |
Family
ID=74033815
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011413243.XA Active CN112199079B (en) | 2020-12-07 | 2020-12-07 | System docking method, computing device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112199079B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113377369A (en) * | 2021-05-17 | 2021-09-10 | 广州有信科技有限公司 | Universal method and device for interfacing third-party service system and terminal equipment |
| CN117118962B (en) * | 2023-07-25 | 2024-03-22 | 领悦数字信息技术有限公司 | Method and system for deploying user methods across multiple cloud platforms |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090298465A1 (en) * | 2005-11-03 | 2009-12-03 | Kt Coporation | Legacy cooperation device and processing method |
| CN104267974A (en) * | 2014-10-22 | 2015-01-07 | 新华瑞德（北京）网络科技有限公司 | Method and device for calling business interface |
-
2020
- 2020-12-07 CN CN202011413243.XA patent/CN112199079B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090298465A1 (en) * | 2005-11-03 | 2009-12-03 | Kt Coporation | Legacy cooperation device and processing method |
| CN104267974A (en) * | 2014-10-22 | 2015-01-07 | 新华瑞德（北京）网络科技有限公司 | Method and device for calling business interface |
Non-Patent Citations (2)
| Title |
|---|
| Adapting Service Requests to Actual Service Interfaces through Semantic;Luca Cavallaro;《2009 ICSE Workshop on Principles of Engineering Service Oriented Systems》;20090519;全文 * |
| 关于多系统对接问题的处理经验及分析;张飞翔;《信息系统工程》;20150131;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112199079A (en) | 2021-01-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9398087B1 (en) | Secure deployment of an application across deployment locations | |
| CN108471395B (en) | Method and device for realizing authentication/authorization, cloud computing system and computer system | |
| US10387670B2 (en) | Handling sensitive data in an application using external processing | |
| US20200004665A1 (en) | Unit test framework for testing code in a gateway service | |
| CN107613005B (en) | Reverse proxy method and device, electronic device and storage medium | |
| CN112199079B (en) | System docking method, computing device and storage medium | |
| US11048885B2 (en) | Cognitive translation service integrated with context-sensitive derivations for determining program-integrated information relationships | |
| CN108733449B (en) | Method, apparatus, and computer-readable storage medium for managing virtual machines | |
| CN109831466B (en) | Micro-service business processing method and nginx server | |
| US11159620B2 (en) | Blockchain based data transformation | |
| US10089293B2 (en) | QR code loading of form elements | |
| US10248535B2 (en) | On-demand automated locale seed generation and verification | |
| US20190075086A1 (en) | Secure message handling of an application across deployment locations | |
| US10664336B2 (en) | System, method and computer program product for adaptive application log analysis | |
| US20090248741A1 (en) | Method and system for integrating an external service | |
| CN114285582A (en) | Information validity checking method and device, storage medium and electronic equipment | |
| CN110780915B (en) | Data processing method, device and storage medium | |
| US11803786B2 (en) | Enterprise integration platform | |
| US10168999B2 (en) | Software object definition and integration | |
| CN113535565B (en) | Interface use case generation method, device, equipment and medium | |
| CN114816361A (en) | Method, device, equipment, medium and program product for generating splicing project | |
| US20200192784A1 (en) | Estimating the number of coding styles by analyzing source code | |
| CN113919310A (en) | Short message content determination method and device, electronic equipment and storage medium | |
| US10169018B2 (en) | Downloading a package of code | |
| CN116049837B (en) | Trusted computing system and method, electronic 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |