CN114640720A - Service protocol switching method and device - Google Patents

Abstract

The invention discloses a service protocol switching method and device, and relates to the technical field of computers. A specific implementation of the method includes: determining a service publisher corresponding to the publishing package according to the configured publishing package based on the first protocol, where the first protocol is a protocol different from the second protocol currently based on the service; The service publisher corresponding to the package loads the publishing package to publish the service according to the first protocol; and processes the received request through the service based on the first protocol. This embodiment can optimize the underlying program, reduce the occupied memory, reduce the research and development difficulty and maintenance cost, and shorten the research and development time.

Description

Method and device for switching service protocol

technical field

The present invention relates to the field of computer technology, and in particular, to a service protocol switching method and device.

Background technique

For a tenanted system, the service protocol needs to be switched frequently in multi-tenant and multi-scenarios. The current service agreement switching solution is to pull multiple branches of the project, and each branch corresponds to a service agreement. The later maintenance costs are high and there are code inconsistencies.

In the process of realizing the present invention, the inventor found that there are at least the following problems in the prior art:

The adaptation of the protocol layer makes the underlying program of the project bloated, and there will be a strong dependence on the framework in the project, and the memory occupied is large, the research and development is difficult, the research and development time is long, and the maintenance cost is high.

SUMMARY OF THE INVENTION

In view of this, the embodiments of the present invention provide a service protocol switching method and device, which can optimize the underlying program, decouple the dependence on the worker scheduling framework, reduce memory occupation, reduce research and development difficulty and maintenance cost, and shorten research and development time.

To achieve the above object, according to an aspect of the embodiments of the present invention, a method for switching a service protocol is provided.

A service protocol switching method, comprising: determining a service publisher corresponding to the publishing package according to a configured publishing package based on a first protocol, where the first protocol is different from a second protocol currently based on a service protocol; loading the publishing package through the service publisher corresponding to the publishing package to publish the service according to the first protocol; processing the received request through the service based on the first protocol.

Optionally, before determining the service publisher corresponding to the release package according to the configured release package based on the first protocol, the step includes: acquiring the configured release package based on the first protocol from a dependent package management plug-in. , and the configuration file in the preset path is loaded by the configuration file loader, where the configuration file includes the initialization file of the service publisher corresponding to the publishing package.

Optionally, before loading the publishing package through the service publisher corresponding to the publishing package to publish the service according to the first protocol, the step includes: pre-configuring the initialization files of multiple service publishers in a in the configuration file.

Optionally, the loading the publishing package through a service publisher corresponding to the publishing package to publish the service according to the first protocol includes: according to the configuration file corresponding to the publishing package The initialization file of the service publisher, dynamically loads the specific implementation class of the service publisher corresponding to the publishing package, so as to publish the service according to the first protocol.

Optionally, the processing of the received request through the service based on the first protocol includes: determining the type of the request according to the first protocol; parsing the request according to a parsing rule corresponding to the type of the request. The request is obtained to obtain the executor identifier, which is the identifier of the executor used to process the request; according to the executor identifier, the corresponding executor name is searched from the executor name finder, and the The request is routed to the executor instance corresponding to the executor name for processing.

Optionally, the routing the request to the executor instance corresponding to the executor name for processing includes: retrieving the corresponding executor instance from the spring container according to the executor name, or through a reflection mechanism to complete the instantiation of the executor to create the executor instance; the request is processed through the executor instance.

According to another aspect of the embodiments of the present invention, an apparatus for switching a service protocol is provided.

A service protocol switching device, comprising: a service publisher determining module, configured to determine a service publisher corresponding to the publishing package according to a configured publishing package based on a first protocol, wherein the first protocol is a service current a different protocol based on the second protocol; a release package loading module, configured to load the release package through a service publisher corresponding to the release package, so as to release the service according to the first protocol; a request processing module, for processing the received request by the service based on the first protocol.

Optionally, it also includes an initialization module, which is used to: obtain the configured release package based on the first protocol from the dependency package management plug-in, and load the configuration file in the preset path through the configuration file loader, the configuration file The initialization file of the service publisher corresponding to the publishing package is included.

Optionally, the initialization module is further configured to: preconfigure the initialization files of multiple service publishers in the configuration file.

Optionally, the publishing package loading module is further configured to: dynamically load the specific implementation of the service publisher corresponding to the publishing package according to the initialization file of the service publisher corresponding to the publishing package in the configuration file class to publish the service according to the first protocol.

Optionally, the request processing module is further configured to: determine the type of the request according to the first protocol; parse the request according to a parsing rule corresponding to the type of the request to obtain an executor identifier, the The executor identifier is the identifier of the executor used to process the request; according to the executor identifier, the corresponding executor name is searched from the executor name finder, and the request is routed to the corresponding executor name. Executor instance for processing.

Optionally, the request processing module is further configured to: retrieve the corresponding executor instance from the spring container according to the executor name, or complete the instantiation of the executor through a reflection mechanism to create the An executor instance; the request is processed through the executor instance.

According to yet another aspect of the embodiments of the present invention, an electronic device is provided.

An electronic device comprising: one or more processors; a memory for storing one or more programs that, when executed by the one or more processors, cause the one or more programs The multiple processors implement the service protocol switching method provided by the embodiment of the present invention.

According to yet another aspect of the embodiments of the present invention, a computer-readable medium is provided.

A computer-readable medium on which a computer program is stored, and when the computer program is executed by a processor, implements the service protocol switching method provided by the embodiment of the present invention.

An embodiment of the above invention has the following advantages or beneficial effects: according to the configured release package based on the first protocol, the service publisher corresponding to the release package is determined, and the first protocol is different from the second protocol on which the service is currently based. protocol; loading the publishing package through the service publisher corresponding to the publishing package to publish the service according to the first protocol; processing the received request through the service based on the first protocol. It can optimize the underlying program, decouple the dependence on the worker scheduling framework, and the framework used is completely non-intrusive for production projects, and there is no need to increase protocol support or adaptation to worker services in order to switch protocols, reducing memory. Occupy, reduce research and development difficulty and maintenance costs, and shorten research and development time.

Further effects of the above non-conventional alternatives will be described below in conjunction with specific embodiments.

Description of drawings

The accompanying drawings are used for better understanding of the present invention and do not constitute an improper limitation of the present invention. in:

1 is a schematic diagram of main steps of a method for switching a service protocol according to an embodiment of the present invention;

2 is a schematic diagram of the architecture of a worker adapter kernel package according to an embodiment of the present invention;

3 is a schematic flowchart of a handover service protocol according to an embodiment of the present invention;

4 is a schematic diagram of the architecture of a handover service protocol according to an embodiment of the present invention;

5 is a schematic diagram of the architecture of a search executor according to an embodiment of the present invention;

6 is a schematic diagram of the architecture of a service publisher according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of main modules of a device for switching a service protocol according to an embodiment of the present invention;

FIG. 8 is an exemplary system architecture diagram to which an embodiment of the present invention may be applied;

FIG. 9 is a schematic structural diagram of a computer system suitable for implementing a terminal device or a server according to an embodiment of the present invention.

Detailed ways

Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, which include various details of the embodiments of the present invention to facilitate understanding and should be considered as exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted from the following description for clarity and conciseness.

FIG. 1 is a schematic diagram of main steps of a method for switching a service protocol according to an embodiment of the present invention.

As shown in FIG. 1 , a method for switching a service protocol according to an embodiment of the present invention mainly includes the following steps S101 to S103.

Step S101: Determine a service publisher corresponding to the publishing package according to the configured publishing package based on the first protocol, where the first protocol is a protocol different from the second protocol on which the service is currently based.

Before determining the service publisher corresponding to the release package according to the configured release package based on the first protocol, the method may include: obtaining the configured release package based on the first protocol from the dependency package management plug-in, and loading the pre-configured release package through the configuration file loader. Set the configuration file in the path, and the configuration file includes the initialization file of the service publisher corresponding to the release package.

A service publisher (ServerPublisher) is used to publish a service through a certain protocol, and the service can be called a service based on the protocol.

Step S102: Load the publishing package through the service publisher corresponding to the publishing package, so as to publish the service according to the first protocol.

Before the publishing package is loaded by the service publisher corresponding to the publishing package to publish the service according to the first protocol, the method may include: preconfiguring the initialization files of multiple service publishers in the configuration file.

Loading the publishing package by the service publisher corresponding to the publishing package to publish the service according to the first protocol may include: dynamically loading the service publishing corresponding to the publishing package according to the initialization file of the service publisher corresponding to the publishing package in the configuration file The concrete implementation class of the server to publish the service according to the first protocol.

Step S103: Process the received request through the service based on the first protocol.

The service based on the first protocol may be a worker (timing) service.

Processing the received request through the service based on the first protocol may include: determining the type of the request according to the first protocol, the types of requests corresponding to different protocols are different; (Invoker) identifier, the executor identifier is the identifier of the executor used to process the request. For example, when the published service protocol is the http service, the type of the request is the type of the http service, and the corresponding parsing rule is the parsing http service. URI, the URI of http contained in the request is parsed as routerkey (that is, the identifier of the executor); if the published service protocol is jsf or dubbo protocol, the request type is jsf or dubbo protocol, and the corresponding The parsing rule is to parse the alias (alias) used by the RPC (Remote Procedure Call Protocol), then the alias used by the RPC contained in the request is parsed as the routerkey; the corresponding executor name (InvokerName) finder is searched according to the executor identifier. the executor name, and route the request to the executor instance corresponding to the executor name for processing.

Routing the request to the executor instance corresponding to the executor name for processing can include: retrieving the corresponding executor instance from the spring container according to the executor name, or completing the instantiation of the executor through the reflection mechanism to create an execution The executor instance includes a method for processing the received request; the request is processed through the executor instance.

In one embodiment, according to the configured release package based on the first protocol, a service publisher corresponding to the release package is determined, and the configured release package based on the first protocol is obtained from the dependency package management plug-in, where the first protocol is and service The second protocol currently based on is a different protocol. Specifically, determine the required service protocol according to the usage environment, configure the release package of the service protocol (ie the first protocol) into the dependent package management plug-in, and replace the original service protocol (ie the second protocol) in the dependent package management plug-in protocol), so as to obtain the configured release package based on the service protocol from the dependency package management plugin as the worker adapter kernel package (worker-adapter-core), where the worker adapter kernel package is used to configure the service protocol in the worker service . The architecture of the worker adapter kernel package according to an embodiment of the present invention is shown in Figure 2. The release package of the service protocol can be a rest (Representational State Transfer, a software architecture style) service release package, dubbo (a high Service framework with excellent performance) protocol release package, jsf (a standard framework for building Java Web applications) release package and other release packages. In the case of using the spring (an open source J2EE application framework) container, the release package of the service protocol can be used as a worker adapter to adapt the spring package (worker-adapter-spring) to obtain the worker adapter kernel package through the spring container . Among them, the worker adapter adaptation spring package is the worker adapter kernel package when hosted in spring.

In one embodiment, the initialization files of multiple service publishers are pre-configured in the configuration file, the configuration files in the preset path are loaded by the configuration file loader, and the configuration files include the initialization files of the service publishers corresponding to the release package . After the worker adapter is started, the configuration file in the preset path can be loaded through the configuration file loader to initialize the service publisher corresponding to the release package through the initialization executor manager, and complete the executor name lookup Data initialization for the executor and executor instance finder for use of the service publisher in subsequent processes, as well as the executor name finder and executor instance finder. Among them, the worker adapter is a wrapper class defined in the worker service, which is used to wrap objects with incompatible interfaces. The wrapped object can be an adapted class. The executor manager is provided with a service publisher API layer, where Including multiple service publishers such as dubbo protocol publisher, jsf protocol publisher, and rest service protocol publisher. In the case of using the spring container for hosting, the default path can be determined according to the variable (ie worker.config.path) configured by the user in the spring container context. If the default path is not configured, the default path is the default Path (ie worker.config.properties).

FIG. 3 is a schematic flowchart of a handover service protocol according to an embodiment of the present invention.

As shown in Figure 3, in the worker (ie timing) service, start the worker launcher (ie the worker adapter launcher), the worker adaptor launcher is the entry point for the worker service to start, and it is also the unification of the loading, publishing and processing of the kernel service. Scheduling entry, the internal processes are all executed by the worker initiator, which provides a unified entry for the worker service. Trigger the configuration file loader to load the configuration file, complete the initialization of the service publisher corresponding to the release package by loading the initialization file of the service publisher corresponding to the release package, and obtain the service publisher corresponding to the release package. The publishing package of the service protocol is dynamically loaded in the manner of SPI (Serial Peripheral Interface) by the service publisher corresponding to the publishing package, so as to publish the service protocol. Receive the pending request, and obtain the routerkey (that is, the executor identifier) in the request based on the published service protocol. Find the corresponding executor name in the executor name finder according to the routerkey, obtain the executor instance in the executor instance finder based on the found executor name, and execute the method in the executor instance to process the received request. The modification of the service protocol of the worker can be realized by the embodiment of the present invention, which can be completed only by modifying the configuration file, and other code layers do not need any modification, thereby realizing the purpose of zero-code one-key switching.

In one embodiment, the type of the request is determined according to the first protocol, and the request is parsed according to a parsing rule corresponding to the type of the request to obtain an executor identifier, where the executor identifier is an identifier of an executor for processing the request. For example, if the published service protocol is the http service, and the type of the request is the type of the http service, the http URI contained in the request will be parsed as the routerkey; if the published service protocol is the jsf or dubbo protocol , the type of the request is jsf or the type of the dubbo protocol, then the alias (alias) used by the RPC (Remote Procedure Call Protocol) contained in the request is parsed as the routerkey. Among them, routerkey is the key of the configuration file, which is the unique identifier of the executor in the worker service.

In one embodiment, according to the name of the executor, the corresponding executor instance is retrieved from the spring container, or the executor instance is instantiated through the reflection mechanism to create the executor instance, and the request is processed through the executor instance. Specifically, in the case of using spring hosting, you can retrieve the corresponding executor instance through the built-in spring container according to the executor name, and complete the creation of the executor instance through the default reflection mechanism.

In one embodiment, the dependency package management plugin may be a maven (project management tool) plugin, and the maven plugin may configure multiple environments according to the dependency packages (ie release packages) used as needed, and different dependency packages may be used in each environment , activate the service agreement that needs to be used through maven's profiles (personalized environment).

FIG. 4 is a schematic structural diagram of a handover service protocol according to an embodiment of the present invention.

As shown in Figure 4, the protocol enumeration class includes service protocols such as http, jsf, and dubbo. The service configuration includes configuration files, and the protocol is configured according to the required service protocol. The protocol configuration manager includes multiple service publishers, service configuration The loader (that is, the configuration file loader) is used to load the configuration file, and the service configuration loader interface is used to configure the preset path.

FIG. 5 is a schematic diagram of the architecture of a search executor according to an embodiment of the present invention.

As shown in Figure 5, the executor is used to process the message class, which can specifically process the received request. The service instance factory (BeanFactoryAware) includes multiple executor instances, and the default executor finder (DefaultInvokerFinder) is used to find the executor that processes the request. (Invoker), the spring context instance finder (SpringInvokerFinder) and the default instance finder are used to find the specific instance of the executor, the instance name finder (BeanNameFinder) is used to find the name of the executor instance, and the executor finder (InvokerFinder) interface is used for To connect with the InvokerManager (InvokerManager).

FIG. 6 is a schematic diagram of the architecture of a service publisher according to an embodiment of the present invention.

As shown in Figure 6, the service publisher API layer can be located in the executor manager, and its specific implementation classes include multiple service publishers such as dubbo protocol publisher, jsf protocol publisher, and rest service protocol publisher. The service publisher configures the instance initializer (initializingBean), which is an interface in spring that can further adjust the instance of the bean.

FIG. 7 is a schematic diagram of main modules of an apparatus for switching a service protocol according to an embodiment of the present invention.

As shown in FIG. 7 , an apparatus 700 for switching a service protocol according to an embodiment of the present invention mainly includes: a service publisher determining module 701 , a publishing package loading module 702 , and a request processing module 703 .

The service publisher determining module 701 is configured to determine a service publisher corresponding to the publishing package according to the configured publishing package based on the first protocol, where the first protocol is a protocol different from the second protocol currently based on the service.

The publishing package loading module 702 is configured to load the publishing package through the service publisher corresponding to the publishing package, so as to publish the service according to the first protocol.

The request processing module 703 is configured to process the received request through the service based on the first protocol.

In one embodiment, an initialization module may also be included, configured to: obtain the configured release package based on the first protocol from the dependency package management plug-in, and load the configuration file in the preset path through the configuration file loader, where the configuration file includes The initialization file of the service publisher corresponding to the distribution package.

In one embodiment, the initialization module is specifically configured to: preconfigure the initialization files of multiple service publishers in the configuration file.

In one embodiment, the release package loading module 702 is specifically configured to: dynamically load the specific implementation class of the service publisher corresponding to the release package according to the initialization file of the service publisher corresponding to the release package in the configuration file, to A protocol publishing service.

In one embodiment, the request processing module 703 is specifically configured to: determine the type of the request according to the first protocol; parse the request according to a parsing rule corresponding to the type of the request to obtain an executor identifier, where the executor identifier is used for processing the request The identifier of the executor; according to the executor identifier, the corresponding executor name is searched from the executor name finder, and the request is routed to the executor instance corresponding to the executor name for processing.

In one embodiment, the request processing module 703 is specifically configured to: retrieve the corresponding executor instance from the spring container according to the executor name, or complete the instantiation of the executor through the reflection mechanism to create the executor instance; The executor instance processes the request.

In addition, the specific implementation content of the device for switching the service protocol in the embodiment of the present invention has been described in detail in the above method for switching the service protocol, so the repeated content will not be described here.

FIG. 8 shows an exemplary system architecture 800 of a service protocol switching method or a service protocol switching apparatus to which embodiments of the present invention can be applied.

As shown in FIG. 8 , the system architecture 800 may include terminal devices 801 , 802 , and 803 , a network 804 and a server 805 . The network 804 is a medium used to provide a communication link between the terminal devices 801 , 802 , 803 and the server 805 . Network 804 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

The user can use the terminal devices 801, 802, 803 to interact with the server 805 through the network 804 to receive or send messages and the like. Various communication client applications may be installed on the terminal devices 801 , 802 and 803 , such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only examples).

The terminal devices 801, 802, 803 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

The server 805 may be a server that provides various services, such as a background management server that provides support for shopping websites browsed by the terminal devices 801 , 802 and 803 (just an example). The background management server can analyze and process the received product information query request and other data, and feed back the processing results (such as target push information, product information—just an example) to the terminal device.

It should be noted that the method for switching the service protocol provided by the embodiment of the present invention is generally performed by the server 805 , and accordingly, the device for switching the service protocol is generally set in the server 805 .

It should be understood that the numbers of terminal devices, networks and servers in FIG. 8 are merely illustrative. There can be any number of terminal devices, networks and servers according to implementation needs.

Referring to FIG. 9 below, it shows a schematic structural diagram of a computer system 900 suitable for implementing a terminal device or a server according to an embodiment of the present invention. The terminal device or server shown in FIG. 9 is only an example, and should not impose any limitations on the functions and scope of use of the embodiments of the present invention.

As shown in FIG. 9, a computer system 900 includes a central processing unit (CPU) 901, which can be loaded into a random access memory (RAM) 903 according to a program stored in a read only memory (ROM) 902 or a program from a storage section 908 Instead, various appropriate actions and processes are performed. In the RAM 903, various programs and data necessary for the operation of the system 900 are also stored. The CPU 901 , the ROM 902 , and the RAM 903 are connected to each other through a bus 904 . An input/output (I/O) interface 905 is also connected to bus 904 .

The following components are connected to the I/O interface 905: an input section 906 including a keyboard, a mouse, etc.; an output section 907 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 908 including a hard disk, etc. ; and a communication section 909 including a network interface card such as a LAN card, a modem, and the like. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the I/O interface 905 as needed. A removable medium 911, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is mounted on the drive 910 as needed so that a computer program read therefrom is installed into the storage section 908 as needed.

In particular, the processes described above with reference to the flowcharts may be implemented as computer software programs in accordance with the disclosed embodiments of the present invention. For example, embodiments disclosed herein include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the method illustrated in the flowchart. In such an embodiment, the computer program may be downloaded and installed from the network via the communication portion 909, and/or installed from the removable medium 911. When the computer program is executed by the central processing unit (CPU) 901, the above-described functions defined in the system of the present invention are executed.

It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the above two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or a combination of any of the above. More specific examples of computer readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Programmable read only memory (EPROM or flash memory), fiber optics, portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the present invention, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present invention, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code therein. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device . Program code embodied on a computer readable medium may be transmitted using any suitable medium including, but not limited to, wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more logical functions for implementing the specified functions executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks 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 is also noted that each block of the block diagrams or flowchart illustrations, and combinations of blocks in the block diagrams or flowchart illustrations, can be implemented in special purpose hardware-based systems that perform the specified functions or operations, or can be implemented using A combination of dedicated hardware and computer instructions is implemented.

The modules involved in the embodiments of the present invention may be implemented in a software manner, and may also be implemented in a hardware manner. The described modules can also be set in the processor, for example, it can be described as: a processor includes a service publisher determining module, a publishing package loading module, and a request processing module. Wherein, the names of these modules do not constitute a limitation of the module itself under certain circumstances. For example, the service publisher determination module can also be described as "used to determine and publish according to the configured publishing package based on the first protocol. The module of the service publisher corresponding to the package".

As another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or may exist alone without being assembled into the device. The above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by a device, the device includes: according to the configured release package based on the first protocol, determine the service corresponding to the release package Publisher, the first protocol is a different protocol from the second protocol that the service is currently based on; the publishing package is loaded by the service publisher corresponding to the publishing package to publish the service according to the first protocol; the service processing based on the first protocol receives request.

According to the technical solution of the embodiment of the present invention, a service publisher corresponding to the publishing package is determined according to the configured publishing package based on the first protocol, where the first protocol is a different protocol from the second protocol on which the service is currently based; The service publisher corresponding to the package loads the publishing package to publish the service according to the first protocol; and processes the received request through the service based on the first protocol. It can optimize the underlying program, reduce memory usage, reduce R&D difficulty and maintenance cost, and shorten R&D time.

The above-mentioned specific embodiments do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modifications, equivalent replacements and improvements made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims (10)

1. a switching method of service agreement, is characterized in that, comprises: determining a service publisher corresponding to the publishing package according to the configured publishing package based on the first protocol, where the first protocol is a protocol different from the second protocol on which the service is currently based; Loading the publishing package through a service publisher corresponding to the publishing package, so as to publish the service according to the first protocol; The received request is processed by the service based on the first protocol. 2. The method according to claim 1, wherein, before determining the service publisher corresponding to the publishing package according to the configured publishing package based on the first protocol, the method comprises: Obtain the configured release package based on the first protocol from the dependency package management plug-in, and load the configuration file in the preset path through the configuration file loader, where the configuration file includes the service publisher corresponding to the release package. initialization file. 3. The method according to claim 2, characterized in that before the publishing the service according to the first protocol by loading the publishing package through a service publisher corresponding to the publishing package, the method comprises: The initialization files of multiple service publishers are pre-configured in the configuration file. 4. The method according to claim 2, characterized in that, loading the publishing package through a service publisher corresponding to the publishing package to publish the service according to the first protocol, comprising: According to the initialization file of the service publisher corresponding to the publishing package in the configuration file, the specific implementation class of the service publisher corresponding to the publishing package is dynamically loaded to publish the service according to the first protocol. 5. The method of claim 1, wherein the processing of the received request through the service based on the first protocol comprises: determining the type of the request according to the first protocol; Parse the request according to a parsing rule corresponding to the type of the request to obtain an executor identifier, where the executor identifier is an identifier of an executor used to process the request; The corresponding executor name is searched from the executor name finder according to the executor identifier, and the request is routed to the executor instance corresponding to the executor name for processing. 6. The method according to claim 5, wherein the routing the request to the executor instance corresponding to the executor name for processing comprises: According to the executor name, retrieve the corresponding executor instance from the spring container, or complete the instantiation of the executor through the reflection mechanism to create the executor instance; The request is processed by the executor instance. 7. A switching device for a service agreement, characterized in that, comprising: a service publisher determining module, configured to determine a service publisher corresponding to the publishing package according to the configured publishing package based on the first protocol, where the first protocol is a protocol different from the second protocol that the service is currently based on; a release package loading module, configured to load the release package through a service publisher corresponding to the release package, so as to release the service according to the first protocol; A request processing module for processing the received request through the service based on the first protocol. 8. The device according to claim 7, further comprising an initialization module for: Obtain the configured release package based on the first protocol from the dependency package management plug-in, and load the configuration file in the preset path through the configuration file loader, where the configuration file includes the service publisher corresponding to the release package. initialization file. 9. An electronic device, characterized in that, comprising: one or more processors; storage means for storing one or more programs, The one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-6. 10. A computer-readable medium on which a computer program is stored, characterized in that, when the computer program is executed by a processor, the method according to any one of claims 1-6 is implemented.

Images