CN112256351B - Method for realizing Feign component, method and device for calling micro-service - Google Patents
Method for realizing Feign component, method and device for calling micro-service Download PDFInfo
- Publication number
- CN112256351B CN112256351B CN202011159522.8A CN202011159522A CN112256351B CN 112256351 B CN112256351 B CN 112256351B CN 202011159522 A CN202011159522 A CN 202011159522A CN 112256351 B CN112256351 B CN 112256351B
- Authority
- CN
- China
- Prior art keywords
- feign
- service
- meta
- component
- micro
- 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
- 238000000034 method Methods 0.000 title claims abstract description 232
- 235000006719 Cassia obtusifolia Nutrition 0.000 claims abstract description 85
- 235000014552 Cassia tora Nutrition 0.000 claims abstract description 85
- 244000201986 Cassia tora Species 0.000 claims abstract description 85
- 230000006870 function Effects 0.000 claims description 24
- 230000008569 process Effects 0.000 claims description 16
- 238000004891 communication Methods 0.000 claims description 12
- 238000012545 processing Methods 0.000 claims description 9
- 241000412611 Consul Species 0.000 description 12
- 235000010627 Phaseolus vulgaris Nutrition 0.000 description 7
- 244000046052 Phaseolus vulgaris Species 0.000 description 7
- 239000007858 starting material Substances 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000001514 detection method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
- G06F9/505—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the load
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
Abstract
The application provides a realization method of a Feign component, a micro-service calling method and a device, wherein the realization method comprises the following steps: creating a main class of the Feign component; the method for creating load balancing is implemented under the main class and is used for retrieving the micro service instance corresponding to the meta information according to the meta information. And realizing a first JavaBean under the main class, wherein the first JavaBean realizes a meta-information acquisition method, and the meta-information acquisition method allows for creating a load balancing method call. And the meta information acquisition method is used for acquiring meta information and constructing the connection driver of the service registration and discovery component when the connection driver corresponding to the current service registration and discovery component does not exist. Therefore, the Feign component has the capability of acquiring the meta-information, and the corresponding micro-service example can be determined according to the meta-information, so that the Feign component can realize the more flexible management of the micro-service cluster.
Description
Technical Field
The application relates to the technical field of micro services, in particular to a method for realizing a Feign component, a method and a device for calling the micro services.
Background
In a conventional service architecture, the scale of the service is within the control range of the operation and maintenance personnel. When deploying multiple nodes of a service, setting of service information is typically accomplished using a static configuration. In micro-service applications, both the number of service instances and the network address are dynamically changing, which presents a significant challenge to system operation and maintenance. Dynamic service registration and discovery is therefore particularly important.
Under the SpringCloud framework of the current mainstream, the mutual call between micro services is realized by adopting Feign components. The Feign component obtains the micro-services registered in the service registration and discovery component based on the names of the micro-services.
However, in practical applications, in consideration of other factors such as micro-service governance, when registering with the service registration and discovery component, additional information is often put in the meta-information area of the service registration and discovery component. However, the information in the meta-information area (hereinafter, the information in the meta-information area is referred to as meta-information) may be actually used to implement micro-service invocation, thereby implementing some special functions (such as no-sense upgrade, etc.). However, under the current SpringCloud framework, the Feign component cannot acquire meta-information from the service registration and discovery component, so that the Feign component can only call the corresponding micro-service according to the name of the micro-service, thereby affecting the management of the micro-service cluster.
Disclosure of Invention
The embodiment of the application aims to provide a method for realizing a Feign component, a method and a device for calling micro services, which are used for solving the problem that the conventional Feign component cannot acquire meta-information to realize micro service processing.
The embodiment of the application provides a method for realizing a Feign component, which comprises the following steps: creating a main class of the Feign component; a method for creating load balancing is realized under the main class; the method for creating load balancing is used for retrieving the micro service instance corresponding to the meta information according to the meta information; implementing a first JavaBean under the main class; the first JavaBean is a JavaBean used for creating a Feign client; the method for acquiring the meta information is realized in the first JavaBean, and the method for acquiring the meta information allows the method for creating load balance to be called; the meta information acquisition method is used for acquiring meta information and constructing a connection driver of the service registration and discovery component when the connection driver corresponding to the current service registration and discovery component does not exist.
In the implementation process, a method for creating load balance of a micro service instance corresponding to meta information can be searched according to the meta information by implementing the method under the main class of the Feign component, and an acquisition method of the meta information is implemented under the main class, so that the acquisition method of the meta information can be called by the method for creating load balance. Therefore, the connection driving of the Feign component to the service registration and discovery component is realized through the meta-information acquisition method, so that the meta-information in the meta-information of the service registration and discovery component is acquired, and the method for creating load balancing is further used for calling. Therefore, the Feign component has the capability of acquiring the meta-information, so that the corresponding micro-service example can be determined according to the meta-information, and the Feign component can realize the more flexible management of the micro-service cluster.
Further, implementing the first java bean under the master class includes: creating a first subclass under the main class, wherein the first subclass inherits the Feign client; in the first subclass, implementing an interface definition method of the Feign client; in the first subclass, the method for acquiring meta information is implemented.
In the implementation manner, the first subclass can be fused with the framework by inheriting the Feign client, so that the first subclass meets the standard required by the framework. The method for acquiring the meta-information can be called by a method for creating load balance by realizing the method for defining the interface of the Feign client, and the whole Feign component can be accessed by the method for defining the interface of the Feign client when other methods for acquiring the meta-information are newly added. In this way, the first subclass obtained by the implementation method can meet the framework requirements, and is convenient for the connection of the meta-information acquisition method and the service registration and discovery component, so that the meta-information is acquired, and the method call for creating load balancing is also convenient.
Further, the method further comprises: implementing a second JavaBean under the main class; the second JavaBean is a JavaBean for creating a client factory mode of load balancing; the method for creating load balancing is implemented in the second JavaBean.
Further, implementing the second java bean under the master class includes: creating a second subclass under the main class; providing a first constructor in the second subclass; the parameters of the first constructor comprise a client factory class provided by a framework and a routing configuration class supporting hot loading; implementing a method of creating load balancing within the first constructor; the participation of the method for creating the load balance comprises the meta information.
Further, the method further comprises: a third JavaBean is also realized under the main class; the third JavaBean is a JavaBean for creating a client factory mode supporting load balancing of the retry function; the method for creating load balancing is implemented in the third JavaBean.
Further, implementing a third java bean under the master class includes: creating a third subclass under the primary class; providing a second constructor in the third subclass; parameters of the second constructor include a client factory class provided by the framework, a routing configuration class supporting hot loading, and a load balancing retry factory class providing a retry strategy; implementing a method of creating load balancing within the second constructor; the participation of the method for creating the load balance comprises the meta information.
Further, the method for creating the load balance is provided with an implementation for searching the service balance; and the entry of the realization of searching the service balance is the meta-information and is returned to be an object containing the micro-service example which is searched according to the meta-information and meets the requirements.
Through the implementation process, the micro service instance can be searched through the meta information, so that more flexible micro service call can be realized.
Further, the method further comprises: a plunge configuration is added to the boot program of the Feign component to direct the process into the main class when the item is launched.
In the embodiment of the application, the cut-in configuration is added in the starting program of the Feign component, so that when the project is started, the process can be guided to enter the main class, the acquisition of the meta-information is executed, the search of the micro-service instance is realized according to the meta-information, and the capability of the Feign component is expanded.
The embodiment of the application also provides a micro-service calling method, which comprises the following steps: adding a Feign component implemented according to any of the foregoing implementation methods to the project dependence; when the micro-service is invoked, the Feign component is started to determine the needed micro-service instance.
Through the implementation process, the application can realize micro-service call based on meta-information when the micro-service is called, thereby realizing more flexible and rich functions than the existing call mode based on the micro-service name.
Further, after adding the Feign component to the dependency of the item, the method further comprises: and adding an enabling item of the Feign component in a configuration file of the item, and setting enabling item to enable.
In the implementation process, the configuration of the Feign component can be realized by configuring the enabling item, and the start-stop control of the capability of carrying out micro-service query on the Feign component based on meta-information is realized, so that an operator is given more abundant operation choices.
The embodiment of the application also provides a micro-service calling method which is applied to the Feign component realized according to the realization method and comprises the following steps: when a micro-service call request is received, a method for creating load balancing of the Feign component calls the meta-information obtaining method to obtain meta-information corresponding to the micro-service call request from the service registration and discovery component; the method for creating load balancing retrieves the micro-service instance corresponding to the meta-information according to the meta-information; and returning the object of the micro service example.
Through the implementation manner, the Feign component has the capability of acquiring the meta-information from the meta-information area of the service registration and discovery component, the meta-information corresponding to the micro-service call request can be acquired from the service registration and discovery component, and then the micro-service instance corresponding to the meta-information is searched according to the meta-information, so that the Feign component can realize more flexible management of the micro-service cluster.
Further, the method for acquiring the meta-information from the service registration and discovery component includes: invoking an acquisition method of the meta information; the meta information obtaining method judges whether a connection driver corresponding to the current service registration and discovery component exists or not; if so, acquiring meta-information corresponding to the micro-service call request from the service registration and discovery component; if the micro-service call request does not exist, a connection driver of the service registration and discovery component is constructed, and meta-information corresponding to the micro-service call request is acquired from the service registration and discovery component.
In the implementation process, the Feign component and the service registration and discovery component can be directly connected by acquiring the connection drive for constructing the service registration and discovery component, so that the Feign component can effectively acquire meta information in the service registration and discovery component.
The embodiment of the application also provides a device for realizing the Feign component, which comprises the following components: creating a module and an implementation module; the creation module is used for creating a main class of the Feign component; a method for creating load balancing is realized under the main class; the implementation module is used for implementing the first JavaBean under the main class; the first JavaBean is a JavaBean used for creating a Feign client; the method for acquiring the meta information is realized in the first JavaBean, and the method for acquiring the meta information allows the method for creating load balance to be called; the meta information acquisition method is used for acquiring meta information and constructing a connection driver of the service registration and discovery component when the connection driver corresponding to the current service registration and discovery component does not exist.
The embodiment of the application also provides a micro-service calling device, which comprises: an adding module and a determining module; the adding module is used for adding the Feign component realized by the realization method according to any one of the above to the dependence of the item; and the determining module is used for starting the Feign component to determine the needed micro service instance when the micro service is called.
The embodiment of the application also provides a Feign component realized by the realization method, which comprises the following steps: the processing module is used for calling the meta-information acquisition method to acquire meta-information corresponding to the micro-service call request from the service registration and discovery component when the micro-service call request is received; the processing module is further used for retrieving a micro service instance corresponding to the meta information according to the meta information; and the return module is used for returning the object of the micro service example.
The embodiment of the application also provides electronic equipment, which comprises: a processor, a memory, and a communication bus; the communication bus is used for realizing connection communication between the processor and the memory; the processor is configured to execute one or more programs stored in the memory to implement any of the methods described above.
The embodiment of the application also provides a readable storage medium, wherein the readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to realize the method of any one of the above.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and should not be considered as limiting the scope, and other related drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic flow chart of an implementation method of a Feign component according to an embodiment of the present application;
FIG. 2 is a flow chart of a micro service invocation method according to an embodiment of the present application;
FIG. 3 is a flowchart illustrating a method for invoking a micro service according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a device for implementing a Feign component according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a micro service calling device according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application.
Embodiment one:
in order to enable the Feign component to have the capability of acquiring meta-information and realize corresponding micro-service management based on the meta-information, the embodiment of the application provides a method for realizing the Feign component.
Referring to fig. 1, the implementation method of the Feign component provided in the embodiment of the present application includes:
s101: a main class of Feign components is created.
In the embodiment of the application, a main class of the Feign component can be created, and the main class registers the realization of the main class to the framework system, so that the framework enters a relevant function flow and provides the realization of the relevant function for the framework system.
In the embodiment of the application, when the main class is created, the main class can be configured to be automatically loaded, so that the main class can be identified and loaded by the framework.
In the embodiment of the application, when the main class is created, a switch can be configured, so that whether the main class is started or not can be controlled.
In the embodiment of the application, when the main class is created, a method for creating load balancing (hereinafter referred to as a createFeignLoadBasancer method) can be implemented under the main class. In the embodiment of the application, the createFeignLoadBalancer method can search the micro-service instance corresponding to the meta-information according to the meta-information, thereby realizing micro-service call based on the meta-information.
In order to implement the above capability, in the embodiment of the present application, the createFeignLoadBalancer method may be implemented by a create () function. In the createFeignLoadBasancer method, the entry may include the registration name, meta-information, etc. of the micro-service that needs to be invoked, and the return may be an object in the Feign component, such as a micro-service instance.
In the embodiment of the application, the createFeignLoadBasand method can be realized in the JavaBean by creating the JavaBean for global use of the system.
It should be appreciated that in practice, different configurations of service registration and discovery components in different projects often result in different requirements for the required java beans. Some configurations require adaptation of a java bean that does not require support for retry functions, while some configurations require adaptation of a java bean that does require support for retry functions.
In order to meet the actual needs, in the embodiment of the present application, two javabeans (hereinafter referred to as a second JavaBean and a third JavaBean) may be simultaneously implemented under a main class. Wherein the second JavaBean is a JavaBean for creating a client factory mode of load balancing, and the third JavaBean is a JavaBean for creating a client factory mode of load balancing supporting retry functions.
In the embodiment of the application, in order to realize the second JavaBean, the second JavaBean can be realized by creating a second subclass under the main class and providing a first constructor in the second subclass, thereby creating a load balancing method in the first constructor. Wherein the parameters of the first constructor include a client factory class provided by the framework, a routing configuration class supporting hot loading, and the like. In the method for creating load balancing, the participation includes meta-information.
Similarly, to implement the third java bean, the third java bean may be implemented by creating a third subclass under the main class, and providing a second constructor in the third subclass, thereby creating a method of load balancing in the second constructor. Wherein, compared with the first constructor, the parameters of the second constructor comprise a client factory class provided by a framework and a routing configuration class supporting hot loading, and further comprise a load balancing retry factory class providing a retry strategy, so that the retry can be supported. Whereas in the method of creating load balancing, the enrollments also include meta-information.
In the embodiment of the application, in order to ensure that the second subclass and the third subclass can meet the framework standard and can be compatible with the framework, an existing load balancing factory of the framework can be inherited when the second subclass and the third subclass are created.
In the embodiment of the application, the createFeignLoadBalancer method should have an implementation (also called a function or a method) for searching service balance. In the embodiment of the application, the realization of searching for service balance can be realized in the createFeignLoadBalancer method by the existing realization of searching for the micro service instance corresponding to the entry through a certain entry, and compared with the traditional realization of searching for service balance, the realization is different in that the entry is meta-information.
It should be understood that in the actual application process, according to the difference of the actual call request, whether the second java bean or the third java bean needs to be adopted is adapted. Exemplary: for example, for a service class call, a third JavaBean that needs to support a retry function may be adapted; whereas for the heartbeat detection class, a second JavaBean may be adapted that does not need to support the retry function.
It should be understood that in the embodiment of the present application, only the second java bean or only the third java bean may be set. At this time, the scheme of the embodiment of the application can still be implemented in part of the scene.
S102: the first java bean is implemented under the master class.
In the embodiment of the application, the first JavaBean is a JavaBean used for creating the Feign client, and can be globally used by a framework system.
In the embodiment of the application, a meta-information acquisition method is implemented in the first JavaBean, and the meta-information acquisition method allows the creatFeignLoadBasancer method to be called.
In the embodiment of the application, the meta information acquisition method is used for acquiring meta information from the service registration and discovery component. And the server is further used for constructing the connection driver of the service registration and discovery component when the connection driver corresponding to the current service registration and discovery component does not exist.
In the embodiment of the present application, the method for acquiring meta information may include: judging whether a connection driver corresponding to the discovery component is registered by the service; if there is no connection drive, the connection drive is constructed. After the construction is successful, meta information in the meta information area of the service registration and discovery component is acquired. If there is a connection driver, the meta information in the meta information area of the service registration and discovery component is directly acquired.
It should be noted that, if the meta-information acquisition method can achieve meta-information acquisition of multiple service registration and discovery components, before determining whether there is a connection driver corresponding to the service registration and discovery component, there is a process of determining the type of the service registration and discovery component. At this time, it is determined whether or not there is a connection driver corresponding to the service registration and discovery component, that is, whether or not there is a connection driver corresponding to the service registration and discovery component of the type.
For example, in the embodiment of the present application, if the meta information obtaining method is used to obtain meta information from the three service registration and discovery components, namely Consul, nacos and Eureka, the meta information obtaining method may be set as follows:
1. judging whether the service registration and discovery component is Consul;
if yes, judging whether a Consul connection driver exists;
if the Consul connection driver does not exist, constructing the Consul connection driver. And after success, acquiring meta information in the Consul meta information area.
2. Judging whether the service registration and discovery component is Nacos;
if yes, judging whether Nacos connection driving exists;
if there is no Nacos link drive, a Nacos link drive is constructed. After success, the meta information in the Nacos meta information area is obtained.
3. Judging whether the service registration and discovery component is Eureka;
if yes, judging whether a Eureka connection driver exists;
if there is no Eureka connection driver, the Eureka connection driver is constructed. After success, meta information in the Eureka meta information area is acquired.
In the embodiment of the application, the first JavaBean can be realized by creating a subclass under the main class.
For example, the first subclass may be created under the main class, and the first subclass inherits the Feign client provided by the framework, so that the first subclass can be fused with the framework, and meets the standard required by the framework.
Then, in the first subclass, an interface definition method of the Feign client and the aforementioned meta-information acquisition method may be implemented.
In the embodiment of the application, the interface definition method for realizing the Feign client can be realized through an execution () function, the participation of which comprises Http Request, options and the like, and the Options comprise optional configurations such as timeout time and the like.
In the embodiment of the application, the call from the createFeignLoadBasancer method to the meta-information acquisition method is realized through the interface definition method of the Feign client, and in addition, when the meta-information acquisition method is newly added in the later period, the access can be realized through the interface definition method of the Feign client.
In the embodiment of the application, a cut configuration can be added in a starting program of the Feign component when or before the main class is created, so as to guide a process to enter the main class when the project is started.
For example, a spring. Manufacturers file may be added under the resources\META-INF directory of the Feign component, and the relevant configuration added, thereby implementing the addition of the cut-in configuration.
The added relevant configuration may be: the spring framework is notified that windeignconfiguration is loaded at project start-up, and spring framework is notified.
It should be noted that, in the above code, winFeignConfiguration characterizes the main class in the embodiment of the present application.
It should be noted that the above method realizes the new function in the Feign component, and the original processing flow of the Feign component can still be maintained.
It should be understood that the implementation method of the Feign component may be implemented by manual configuration of an engineer, but may also be implemented by presetting a configuration script, so as to implement automatic execution by an electronic device such as a computer.
According to the implementation method of the Feign component, provided by the embodiment of the application, the method for creating load balance of the micro service instance corresponding to the meta information can be retrieved according to the meta information is realized under the main class of the Feign component, the method for acquiring the meta information is realized under the main class, and the method for acquiring the meta information can be called by the method for creating load balance. Therefore, the connection driving of the Feign component to the service registration and discovery component is realized through the meta-information acquisition method, so that the meta-information in the meta-information of the service registration and discovery component is acquired, and the method for creating load balancing is further used for calling. Therefore, the Feign component has the capability of acquiring the meta-information, so that the corresponding micro-service example can be determined according to the meta-information, and the Feign component can realize the more flexible management of the micro-service cluster.
Correspondingly, the embodiment of the application also provides a micro-service calling method which is applied to the Feign component realized according to the realization method.
As shown in fig. 2, the micro service invocation method includes:
s201: when receiving a micro-service call request, the createFeignLoadBalancer method of the Feign component calls a meta-information acquisition method, and the meta-information corresponding to the micro-service call request is acquired from the service registration and discovery component.
It should be understood that, in the embodiment of the present application, when the meta-information corresponding to the micro-service invocation request is acquired from the service registration and discovery component, the meta-information acquiring method first determines whether there is a connection driver corresponding to the current service registration and discovery component. If the micro-service call request exists, the meta-information corresponding to the micro-service call request can be directly obtained from the service registration and discovery component; if the service registration and discovery component does not exist, a connection driver of the service registration and discovery component can be constructed, and then meta-information corresponding to the micro-service call request is acquired from the service registration and discovery component.
It should be understood that, in the embodiment of the present application, the micro service call request will generally have information such as the registration name of the micro service that is requested to be called. Based on information such as the registration name, meta-information related to the micro-service requested to be invoked can be found in the meta-information area.
S202: the method for creating load balancing retrieves the micro-service instance corresponding to the meta-information according to the meta-information.
In the embodiment of the application, the createFeignLoadBalancer method calls the meta-information acquisition method, so that the corresponding micro-service example is obtained by searching.
S203: returning the object of the micro service instance.
It should be noted that, in general, when a certain item is performed, a micro service call needs to be performed, and thus, a Feign component needs to be applied to the item, so that use of the Feign component is achieved. For this reason, in the embodiment of the present application, there is further provided a micro service invocation method, which may be shown in fig. 3, including:
s301: the Feign component implemented according to the foregoing implementation method is added to the dependencies of the project.
It should be understood that in the embodiment of the present application, after the Feign component is added to the dependency of the item, the enable item of the Feign component may be added to the configuration file of the item, and the enable item may be set.
The so-called set enable item enables, i.e. characterizes the turning on of the function of the added add Feign component, whose code value in the program is usually "true". The enable item may be set to off in addition to being enabled, thereby turning off the function of the added add Feign component, whose code value in the program is typically "false".
S302: when the micro-service is invoked, the Feign component is started to determine the required micro-service instance.
When micro service needs to be called in the project, the Feign component can determine the micro service example according to the micro service calling method shown in the figure 2.
It should be understood that the method of fig. 3 may be manually configured by an engineer, but may also be automatically performed by an electronic device such as a computer by presetting a configuration script.
Through the scheme of the embodiment of the application, the Feign component can have the capability of acquiring the meta-information from the meta-information area of the service registration and discovery component, and the selection of the micro-service instance based on the meta-information can be realized, so that the Feign component can realize the more flexible management of the micro-service cluster.
Embodiment two:
the embodiment of the present application is further illustrated by a specific implementation method of the Feign component in combination with the description of the first embodiment.
In this embodiment, the implementation of the Feign component includes the following processes:
1. spring. Industries files are added under the resources\META-INF directory, and relevant configurations are added:
org.springframework.boot.autoconfigure.EnableAutoConfiguration＝com.w inning.base.akso.cloud.client.autoconfigure.WinFeignConfiguration。
2. creating a main class WinFeignConfiguration:
2.1 realizing automatic loading, so that the main class can be identified by the framework and loaded;
2.2 implementing a configuration switch so that the master class can control whether to enable or not through a configuration file;
2.3 implement Bean: cachinglblbclientfactor (second JavaBean):
the role of implementing the cachingclientfactor is to create a client factory mode JavaBean for cacheable load balancing in single instance mode, providing global use to the framework system (implementation referring to process 3).
2.4 implement Bean: retryabeCachingLBClientFactoy (third JavaBean):
the role of implementing retrybebeccientfactory is to create a single instance-mode cacheable load-balancing client factory model java bean that supports retry functions, providing framework system global use (implementation see process 3).
2.5 implement Bean: feignClient (first JavaBean):
the effect of implementing the feignClient is to create a single-instance-mode Feign client JavaBean, which is provided for global use by the framework system (his implementation is windloadbalancefeignclient, first subclass), implementing reference process 4).
3. Creating the subclass WinCachingSpringLoadBalanceFactoy (second subclass and third subclass):
This class provides a specific implementation of two beans, a castingLBClientFactory and a retryabe castingLBClientFactory in a WinFeignConfiguration.
3.1 inherits the CachingSpringLoadBalanceFactory (cacheable load balancing factory), so that the created subclass WinCachingSpringLoadBalanceFactory meets the standard and can be fused with the framework.
3.2 implements the WinCachingSpringLoadBalanceFactory (SpringClientFactory factory, winRoutesConfig winRoutesConfig) method.
It should be noted that, the WinCashingSpringLoadBalanceFactory method is a constructor, and the parameters characterizing the constructor (SpringClientFactory factory, winRoutesConfig winRoutesConfig) include a client factory class SpringClientFactory provided by the framework, and a routing configuration class WinRouteConfig supporting hot loading.
3.3 implementation of WinCachingSpringLoadBalancerFactory (SpringClientFactory factory, loadBalancedRetryFacto loadBalancedRetryPolicyFactory, winRoutesConfig winRouteConfig) method.
It should be noted that, the WinCashingSpringLoadBalanceFacto method is a constructor, and the parameters characterizing the constructor (SpringClientFactory factory, loadBalanceRetryFacto loadBalancedRetryPolicyFactory, winRoutesConfig WinRouteConfig) include a client factory class SpringClientFacto provided by the framework, a routing configuration class WinRouteConfig supporting hot loading, and a LoadBalanceRetryFacto factory class providing a retry strategy.
It should be understood that the WinCachingSpringLoadBalancerFactory method in 3.2 and 3.3 are both constructors, but that in 3.3 there is one more parameter LoadBalanceRetryFactory than in 3.2, so that the constructors of 3.3 have one more capability to support retry than the constructors of 3.2. In an embodiment, the constructor of 3.2 is a first constructor and the constructor of 3.3 is a second constructor.
3.4 implement the createFeignLoadBasancer (String clientName, map < String, collection > header) method.
The createFeignLoadBalancer method is an important implementation in the construction function, the entry is the registration name of the micro service to be called, and the meta information, and the returned is a WinFeignLoadBalancer object.
3.5 implements the findServerBalaner (boolean ifDefault, string clientName, string service, string version, bootean endMode) method.
The findServerBalancer method (i.e., the implementation of finding service balances in the embodiments of the present application) is an important implementation within the createFeignLoadbalancer method. The parametrization of the findServerBalancer method is meta-information, and returned is a WinFeignLoadBalancer object containing micro-service instances retrieved according to the meta-information.
In this embodiment, bean is implemented by 3.1, 3.2, 3.4, and 3.5: cachingnlbclientfactor; bean is realized by 3.1, 3.3, 3.4 and 3.5: retryabeCachingLBClientFactoy.
4. Creating the subclass WinLoadBalancerFeignClient (first subclass):
it should be noted that this class provides beans in WinFeignConfiguration: specific implementation of feignClient.
4.1 inherits the Client so that WinLoadBalancerFeignclient meets the standard and can be fused with the framework.
4.2 implement execution (Request, request. Options) throws IOException method
The execution () throws IOException method is a method defined by a client interface, and is a main method of windloadbalancerfeignclient. The admission is Http Request, and Options. Options include optional configurations such as timeout times.
4.3 implement getMetaInfo method (acquisition of meta information):
judging whether the service registration and discovery component is Consul; if yes, judging whether a Consul connection drive exists. If yes, acquiring meta information of a Consul meta information area; if not, constructing a Consul connection driver, and acquiring meta information of a Consul meta information area.
If the service registration and discovery component is not Consul, judging whether the service registration and discovery component is Nacos; if yes, judging whether Nacos connection driving exists. If so, acquiring meta information of the Nacos meta information area; if not, constructing a Nacos connection driver, and acquiring meta-information of a Nacos meta-information area.
If the service registration and discovery component is not Nacos, judging whether the service registration and discovery component is Eureka; if yes, judging whether the Eureka connection driver exists. If yes, acquiring meta information of the Eureka meta information area; if not, constructing a Eureka connection driver, and acquiring meta information of a Eureka meta information area.
5. The createWinFeignLoadBalaner method calls the getMetaInfo method of WinLoadBalancerFeignClient to acquire the required meta-information.
After the Feign component is implemented through the above-described procedure, the above-described implemented Feign component (since the foregoing implementation is a function of implementing micro service selection based on meta information in the Feign component, instead of the entire Feign component, it is hereinafter referred to as a winner-starter component of the Feign component in this embodiment) is added to the dependency of the item:
<dependencies>
<dependency>
<groupId>com.winning</groupId>
<artifactId>winning-akso-cloud-feign-starter</artifactId>
</dependency>
<dependencies>
code meaning: the target item uses a winner component.
It should be understood that, in this embodiment, besides adding the wining-akso-closed-feign-starter component to the dependency of the item in the above manner, the addition of the wining-akso-closed-feign-starter component to the dependency of the item may also be implemented by directly adding the jar file to the classpath of the target item (put into the lib directory), and the like, which is not limited in the embodiment of the present application.
A winn enabled item is added to the configuration file of the item and its value is set to true. If the winner component is to be shut down, the winner item is set to a value of false.
And entering a Feign component processing flow. Each time the micro services are called with each other, the Feign component obtains the meta information stored in the meta information area of the service registration and discovery component, and then searches the micro service instance according to the meta information.
At present, in the SpringCloud project, the micro services are mutually called, and only the micro service instance can be selected by the registration name of the micro service at the time of registration. By the scheme of the embodiment, besides the registered name, micro service instance selection can be performed through meta information. This lays a foundation for better implementation of complex and special microservice management.
Embodiment III:
based on the same inventive concept, the embodiment of the present application further provides a device 100 for implementing a Feign component and a device 200 for invoking a micro service. Referring to fig. 4 and 5, fig. 4 shows a Feign component implementation apparatus using the Feign component implementation method shown in fig. 1, and fig. 5 shows a micro service invocation apparatus using the micro service invocation method shown in fig. 3 according to the first embodiment. It should be appreciated that the specific functions of the apparatus 100 and the apparatus 200 may be referred to the above description, and detailed descriptions are omitted here as appropriate to avoid repetition. The device 100 and the device 200 comprise at least one software functional module that can be stored in memory in the form of software or firmware or solidified in the operating system of the device 100, 200. Specifically:
Referring to fig. 4, the implementing apparatus 100 of the Feign component includes: a creation module 101 and an implementation module 102. Wherein:
the creation module 101 is configured to create a main class of the Feign component; a method for creating load balancing is realized under the main class;
the implementation module 102 is configured to implement a first java bean under the main class; the first JavaBean is a JavaBean used for creating a Feign client;
the method for acquiring the meta information is realized in the first JavaBean, and the method for acquiring the meta information allows the method for creating load balance to be called; the meta information acquisition method is used for acquiring meta information and constructing a connection driver of the service registration and discovery component when the connection driver corresponding to the current service registration and discovery component does not exist.
In the embodiment of the present application, the implementation module 102 is specifically configured to create a first subclass under the main class, where the first subclass inherits the Feign client; in the first subclass, implementing an interface definition method of the Feign client; in the first subclass, the method for acquiring meta information is implemented.
In the embodiment of the present application, the implementation module 102 is further configured to implement a second java bean under the main class; the second JavaBean is a JavaBean for creating a client factory mode of load balancing; the method for creating load balancing is implemented in the second JavaBean.
In the embodiment of the present application, the implementation module 102 is specifically configured to create a second subclass under the main class; providing a first constructor in the second subclass; the parameters of the first constructor comprise a client factory class provided by a framework and a routing configuration class supporting hot loading; implementing a method of creating load balancing within the first constructor; the participation of the method for creating the load balance comprises the meta information.
In the embodiment of the present application, the implementation module 102 is further configured to implement a third java bean under the main class; the third JavaBean is a JavaBean for creating a client factory mode supporting load balancing of the retry function; the method for creating load balancing is implemented in the third JavaBean.
In the embodiment of the present application, the implementation module 102 is specifically configured to create a third subclass under the main class; providing a second constructor in the third subclass; parameters of the second constructor include a client factory class provided by the framework, a routing configuration class supporting hot loading, and a load balancing retry factory class providing a retry strategy; implementing a method of creating load balancing within the second constructor; the participation of the method for creating the load balance comprises the meta information.
In the embodiment of the application, the method for creating the load balance is provided with the realization of searching the service balance; and the entry of the realization of searching the service balance is the meta-information and is returned to be an object containing the micro-service example which is searched according to the meta-information and meets the requirements.
In the embodiment of the present application, the creation module 101 is further configured to add a plunge configuration in a boot program of the Feign component, so as to guide a process into the main class when the item is started.
Referring to fig. 5, the micro service invocation apparatus 200 includes: an adding module 201 and a determining module 202. Wherein:
the adding module 201 is configured to add a Feign component implemented according to the implementation method of the first embodiment to the dependency of the item;
the determining module 202 is configured to start the Feign component to determine a required micro service instance when the micro service is invoked.
In the embodiment of the present application, the adding module 201 is further configured to add an enable item of the Feign component in a configuration file of the item after adding the Feign component to the dependency of the item, and set the enable item to enable.
Based on the same inventive concept, the embodiment of the present application further provides a Feign component implemented by the implementation method according to the first embodiment, which can implement a function corresponding to the method shown in fig. 2 of the embodiment. Accordingly, a detailed description is appropriately omitted herein to avoid repetition. The modules in the Feign component can be stored in memory in the form of software or firmware or cured in the electronic device in which the Feign component resides. Specifically:
The Feign module comprises:
the processing module is used for calling the meta-information acquisition method to acquire meta-information corresponding to the micro-service call request from the service registration and discovery component when the micro-service call request is received;
the processing module is further used for retrieving a micro service instance corresponding to the meta information according to the meta information;
and the return module is used for returning the object of the micro service example.
In the embodiment of the present application, the method for acquiring meta-information corresponding to the micro-service invocation request from the service registration and discovery component includes:
judging whether a connection driver corresponding to the current service registration and discovery component exists or not;
if so, acquiring meta-information corresponding to the micro-service call request from the service registration and discovery component;
if the micro-service call request does not exist, a connection driver of the service registration and discovery component is constructed, and meta-information corresponding to the micro-service call request is acquired from the service registration and discovery component.
It should be understood that, for simplicity of description, the descriptions in the first embodiment are omitted in this embodiment.
Embodiment four:
This embodiment provides an electronic device, see fig. 6, comprising a processor 601, a memory 602 and a communication bus 603. Wherein:
the communication bus 603 is used to enable connected communication between the processor 601 and the memory 602.
The processor 601 is configured to execute one or more first programs stored in the memory 602 to implement the method of the first and/or second embodiments.
It will be appreciated that the configuration shown in fig. 6 is merely illustrative, and that the electronic device may also include more or fewer components than shown in fig. 6, or have a different configuration than shown in fig. 6. For example, the electronic device may be a server or a terminal.
The present embodiment also provides a readable storage medium, such as a floppy disk, an optical disk, a hard disk, a flash memory, a usb disk, an SD (Secure Digital Memory Card, secure digital Card) Card, an MMC (Multimedia Card) Card, or the like, in which one or more programs implementing the above steps are stored, and the one or more programs may be executed by one or more processors to implement the method in the first and/or second embodiments. And will not be described in detail herein.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The above-described apparatus embodiments are merely illustrative, for example, the division of the units is merely a logical function division, and there may be other manners of division in actual implementation, and for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some communication interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.
Further, the units described as separate units may or may not be physically separate, and units displayed as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
Furthermore, functional modules in various embodiments of the present application may be integrated together to form a single portion, or each module may exist alone, or two or more modules may be integrated to form a single portion.
In this document, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.
Herein, a plurality refers to two or more.
The above description is only an example of the present application and is not intended to limit the scope of the present application, and various modifications and variations will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application.
Claims (16)
1. A method for implementing a Feign component, comprising:
creating a main class of the Feign component; a method for creating load balancing is realized under the main class; the method for creating load balancing is used for retrieving the micro service instance corresponding to the meta information according to the meta information;
implementing a first JavaBean under the main class; the first JavaBean is a JavaBean used for creating a Feign client;
the method for acquiring the meta information is realized in the first JavaBean, and the method for acquiring the meta information allows the method for creating load balance to be called; the method for acquiring the meta information is used for acquiring the meta information and constructing the connection driver of the service registration and discovery component when the connection driver corresponding to the current service registration and discovery component does not exist;
implementing the first java bean under the master class includes:
creating a first subclass under the main class, wherein the first subclass inherits the Feign client;
in the first subclass, implementing an interface definition method of the Feign client;
in the first subclass, the method for acquiring meta information is implemented.
2. The method of implementing a Feign assembly of claim 1, further comprising:
Implementing a second JavaBean under the main class; the second JavaBean is a JavaBean for creating a client factory mode of load balancing;
the method for creating load balancing is implemented in the second JavaBean.
3. The method for implementing the Feign component of claim 2, wherein implementing the second java bean under the master class comprises:
creating a second subclass under the main class;
providing a first constructor in the second subclass; the parameters of the first constructor comprise a client factory class provided by a framework and a routing configuration class supporting hot loading;
implementing a method of creating load balancing within the first constructor; the participation of the method for creating the load balance comprises the meta information.
4. The method of implementing a Feign assembly of claim 1, further comprising:
a third JavaBean is also realized under the main class; the third JavaBean is a JavaBean for creating a client factory mode supporting load balancing of the retry function;
the method for creating load balancing is implemented in the third JavaBean.
5. The method for implementing the Feign component of claim 4, wherein implementing a third java bean under the master class comprises:
Creating a third subclass under the primary class;
providing a second constructor in the third subclass; parameters of the second constructor include a client factory class provided by the framework, a routing configuration class supporting hot loading, and a load balancing retry factory class providing a retry strategy;
implementing a method of creating load balancing within the second constructor; the participation of the method for creating the load balance comprises the meta information.
6. The method for implementing the Feign component according to claim 3 or 5, wherein the method for creating load balancing has an implementation of searching for service balance;
and the entry of the realization of searching the service balance is the meta-information and is returned to be an object containing the micro-service example which is searched according to the meta-information and meets the requirements.
7. The method of implementing a Feign assembly of any one of claims 1-5, further comprising:
a plunge configuration is added to the boot program of the Feign component to direct the process into the main class when the item is launched.
8. A micro service invocation method, comprising:
adding the Feign component implemented by the implementation of any of claims 1-7 to the dependencies of the item;
When the micro-service is invoked, the Feign component is started to determine the needed micro-service instance.
9. The micro service invocation method of claim 8, wherein after adding the Feign component to the dependency of an item, the method further comprises:
and adding an enabling item of the Feign component in a configuration file of the item, and setting enabling item to enable.
10. A micro-service invocation method, applied to a Feign component implemented by the implementation method according to any one of claims 1 to 7, comprising:
when a micro-service call request is received, a method for creating load balancing of the Feign component calls the meta-information obtaining method to obtain meta-information corresponding to the micro-service call request from the service registration and discovery component;
the method for creating load balancing retrieves the micro-service instance corresponding to the meta-information according to the meta-information;
and returning the object of the micro service example.
11. The micro service invocation method of claim 10, wherein the invoking the meta-information retrieval method retrieves meta-information corresponding to the micro service invocation request from the service registration and discovery component, comprising:
Invoking an acquisition method of the meta information;
the meta information obtaining method judges whether a connection driver corresponding to the current service registration and discovery component exists or not;
if so, acquiring meta-information corresponding to the micro-service call request from the service registration and discovery component;
if the micro-service call request does not exist, a connection driver of the service registration and discovery component is constructed, and meta-information corresponding to the micro-service call request is acquired from the service registration and discovery component.
12. A device for implementing a Feign assembly, comprising: creating a module and an implementation module;
the creation module is used for creating a main class of the Feign component; a method for creating load balancing is realized under the main class;
the implementation module is used for implementing the first JavaBean under the main class; the first JavaBean is a JavaBean used for creating a Feign client;
the method for acquiring the meta information is realized in the first JavaBean, and the method for acquiring the meta information allows the method for creating load balance to be called; the method for acquiring the meta information is used for acquiring the meta information and constructing the connection driver of the service registration and discovery component when the connection driver corresponding to the current service registration and discovery component does not exist;
The implementation module is specifically configured to: creating a first subclass under the main class, wherein the first subclass inherits the Feign client; in the first subclass, implementing an interface definition method of the Feign client; in the first subclass, the method for acquiring meta information is implemented.
13. A micro service invocation apparatus, comprising: an adding module and a determining module;
the adding module is used for adding the Feign component realized by the realization method according to any one of claims 1-7 into the dependence of the item;
and the determining module is used for starting the Feign component to determine the needed micro service instance when the micro service is called.
14. A Feign assembly implemented according to the implementation of any one of claims 1-7, comprising:
the processing module is used for calling the meta-information acquisition method to acquire meta-information corresponding to the micro-service call request from the service registration and discovery component when the micro-service call request is received;
the processing module is further used for retrieving a micro service instance corresponding to the meta information according to the meta information;
and the return module is used for returning the object of the micro service example.
15. An electronic device, comprising: a processor, a memory, and a communication bus;
the communication bus is used for realizing connection communication between the processor and the memory;
the processor is configured to execute one or more programs stored in the memory to implement the method of any one of claims 1 to 11.
16. A readable storage medium storing one or more programs executable by one or more processors to implement the method of any of claims 1-11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011159522.8A CN112256351B (en) | 2020-10-26 | 2020-10-26 | Method for realizing Feign component, method and device for calling micro-service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011159522.8A CN112256351B (en) | 2020-10-26 | 2020-10-26 | Method for realizing Feign component, method and device for calling micro-service |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112256351A CN112256351A (en) | 2021-01-22 |
| CN112256351B true CN112256351B (en) | 2023-11-17 |
Family
ID=74261613
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011159522.8A Active CN112256351B (en) | 2020-10-26 | 2020-10-26 | Method for realizing Feign component, method and device for calling micro-service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112256351B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113590236B (en) * | 2021-08-03 | 2023-10-31 | 聚好看科技股份有限公司 | Server and microservice declarative interface timeout configuration method |
| CN114285857B (en) * | 2021-12-31 | 2024-01-26 | 中企云链（北京）金融信息服务有限公司 | Load balancing method, device and system |
Citations (38)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2169931A1 (en) * | 2008-09-24 | 2010-03-31 | Nokia Siemens Networks OY | Method and device for data processing and communication system comprising such device |
| CN101697119A (en) * | 2009-10-12 | 2010-04-21 | 南京联创科技集团股份有限公司 | JavaBean class leading-in form based realization method of replacing traditional URL access address |
| CN102221998A (en) * | 2011-06-07 | 2011-10-19 | 北京大学 | Method for extending EJB container in component running support platform |
| CN103763209A (en) * | 2014-01-03 | 2014-04-30 | 上海聚力传媒技术有限公司 | Scheduling method and device of CDN servers |
| CN105577822A (en) * | 2016-01-27 | 2016-05-11 | 北京国电通网络技术有限公司 | Content distribution network (CDN) node based cache centralized management system |
| CN106254423A (en) * | 2016-07-20 | 2016-12-21 | 普元信息技术股份有限公司 | The method realizing Restful service release quickly based on micro services framework |
| CN107124465A (en) * | 2017-05-12 | 2017-09-01 | 国网江苏省电力公司电力科学研究院 | Towards the distributed photovoltaic remote data acquisition system framework method accessed on a large scale |
| CN107835181A (en) * | 2017-11-16 | 2018-03-23 | 泰康保险集团股份有限公司 | Right management method, device, medium and the electronic equipment of server cluster |
| CN108011967A (en) * | 2017-12-15 | 2018-05-08 | 四川长虹电器股份有限公司 | Picture upload method based on AWS micro services |
| CN108206852A (en) * | 2016-12-20 | 2018-06-26 | 杭州华为数字技术有限公司 | A kind of dialogue-based Service Instance management method and equipment under micro services frame |
| CN108306917A (en) * | 2017-01-13 | 2018-07-20 | 中国移动通信集团江西有限公司 | The register method and device of data processing method and device, micro services module |
| CN108834177A (en) * | 2018-06-08 | 2018-11-16 | 京信通信系统（中国）有限公司 | Load-balancing method, device, computer equipment and storage medium |
| CN108833137A (en) * | 2018-05-18 | 2018-11-16 | 南京南瑞信息通信科技有限公司 | A kind of flexibility micro services Monitoring framework framework |
| CN108920133A (en) * | 2018-06-14 | 2018-11-30 | 北京三快在线科技有限公司 | Across Programming with Pascal Language method, apparatus, electronic equipment and storage medium |
| CN109089163A (en) * | 2018-07-27 | 2018-12-25 | 武汉斗鱼网络科技有限公司 | Barrage message distributing method, device, equipment and storage medium |
| CN109587246A (en) * | 2018-12-06 | 2019-04-05 | 国云科技股份有限公司 | A kind of implementation method of the micro services frame of integrated multiple kinds independent assortment |
| CN109587071A (en) * | 2018-11-30 | 2019-04-05 | 北京工业大学 | Micro services load-balancing method based on SDN |
| CN109636334A (en) * | 2018-12-07 | 2019-04-16 | 深圳市汇鑫科技股份有限公司 | A kind of property intelligence community service system and method |
| CN109660585A (en) * | 2018-09-28 | 2019-04-19 | 深圳壹账通智能科技有限公司 | Call method, device, equipment and the storage medium of AOP enhancing objects services |
| CN109683905A (en) * | 2018-12-24 | 2019-04-26 | 国云科技股份有限公司 | A kind of system method for automatically releasing |
| CN109766080A (en) * | 2019-01-22 | 2019-05-17 | 努比亚技术有限公司 | Micro services register method, device, electronic equipment and readable storage medium storing program for executing |
| CN109814909A (en) * | 2019-01-18 | 2019-05-28 | 南京绿新能源研究院有限公司 | Method based on Spring cloud micro services framework cloud SCADA system |
| CN109995713A (en) * | 2017-12-30 | 2019-07-09 | 华为技术有限公司 | Service processing method and relevant device in a kind of micro services frame |
| CN110048879A (en) * | 2019-03-12 | 2019-07-23 | 平安医疗健康管理股份有限公司 | Micro services register method, device, electronic equipment and computer readable storage medium |
| CN110099099A (en) * | 2019-03-28 | 2019-08-06 | 中国电子科技集团公司电子科学研究院 | For the spatial information micro services encapsulation at terrestrial information port and service integration method |
| CN110149396A (en) * | 2019-05-20 | 2019-08-20 | 华南理工大学 | A kind of platform of internet of things construction method based on micro services framework |
| CN110262972A (en) * | 2019-06-17 | 2019-09-20 | 中国科学院软件研究所 | A kind of failure testing tool and method towards micro services application |
| CN110602178A (en) * | 2019-08-26 | 2019-12-20 | 杭州电子科技大学 | Method for calculating and processing temperature sensor data based on edge compression |
| CN110661780A (en) * | 2019-08-15 | 2020-01-07 | 西安雷迪信息技术有限公司 | Wireless city data sharing method and system based on SAAS application |
| CN110781476A (en) * | 2019-10-15 | 2020-02-11 | 南京南瑞信息通信科技有限公司 | Flexible micro-service security access control method and system |
| CN110971449A (en) * | 2019-10-25 | 2020-04-07 | 武汉烽火众智数字技术有限责任公司 | Service management and control system based on micro-service architecture |
| CN110989983A (en) * | 2019-11-28 | 2020-04-10 | 深圳航天智慧城市系统技术研究院有限公司 | Zero-coding application software rapid construction system |
| CN111158792A (en) * | 2020-01-02 | 2020-05-15 | 普元信息技术股份有限公司 | System and method for realizing dynamic configurable service parameter verification processing under distributed architecture |
| CN111193803A (en) * | 2019-12-31 | 2020-05-22 | 四川省公安科研中心 | Spring group-based micro-service construction method and spring group micro-service framework |
| CN111324577A (en) * | 2018-12-17 | 2020-06-23 | 大唐移动通信设备有限公司 | Method and device for reading and writing Yml file |
| CN111338813A (en) * | 2020-02-10 | 2020-06-26 | 北京字节跳动网络技术有限公司 | Method, device, medium and electronic equipment for dynamically generating middleware |
| CN111352577A (en) * | 2018-12-24 | 2020-06-30 | 杭州海康威视系统技术有限公司 | Object storage method and device |
| CN111414352A (en) * | 2020-03-27 | 2020-07-14 | 北京明略软件系统有限公司 | Database information management method and device |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8250590B2 (en) * | 2007-07-13 | 2012-08-21 | International Business Machines Corporation | Apparatus, system, and method for seamless multiple format metadata abstraction |
| DE102009030019B3 (en) * | 2009-06-23 | 2010-12-30 | Siemens Aktiengesellschaft | System and method for reliable authentication of a device |
| US9350594B2 (en) * | 2013-06-26 | 2016-05-24 | Avaya Inc. | Shared back-to-back user agent |
| US10277582B2 (en) * | 2015-08-27 | 2019-04-30 | Microsoft Technology Licensing, Llc | Application service architecture |
| US10594764B2 (en) * | 2016-09-16 | 2020-03-17 | Oracle International Corporation | Request cache to improve web applications performance |
-
2020
- 2020-10-26 CN CN202011159522.8A patent/CN112256351B/en active Active
Patent Citations (38)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2169931A1 (en) * | 2008-09-24 | 2010-03-31 | Nokia Siemens Networks OY | Method and device for data processing and communication system comprising such device |
| CN101697119A (en) * | 2009-10-12 | 2010-04-21 | 南京联创科技集团股份有限公司 | JavaBean class leading-in form based realization method of replacing traditional URL access address |
| CN102221998A (en) * | 2011-06-07 | 2011-10-19 | 北京大学 | Method for extending EJB container in component running support platform |
| CN103763209A (en) * | 2014-01-03 | 2014-04-30 | 上海聚力传媒技术有限公司 | Scheduling method and device of CDN servers |
| CN105577822A (en) * | 2016-01-27 | 2016-05-11 | 北京国电通网络技术有限公司 | Content distribution network (CDN) node based cache centralized management system |
| CN106254423A (en) * | 2016-07-20 | 2016-12-21 | 普元信息技术股份有限公司 | The method realizing Restful service release quickly based on micro services framework |
| CN108206852A (en) * | 2016-12-20 | 2018-06-26 | 杭州华为数字技术有限公司 | A kind of dialogue-based Service Instance management method and equipment under micro services frame |
| CN108306917A (en) * | 2017-01-13 | 2018-07-20 | 中国移动通信集团江西有限公司 | The register method and device of data processing method and device, micro services module |
| CN107124465A (en) * | 2017-05-12 | 2017-09-01 | 国网江苏省电力公司电力科学研究院 | Towards the distributed photovoltaic remote data acquisition system framework method accessed on a large scale |
| CN107835181A (en) * | 2017-11-16 | 2018-03-23 | 泰康保险集团股份有限公司 | Right management method, device, medium and the electronic equipment of server cluster |
| CN108011967A (en) * | 2017-12-15 | 2018-05-08 | 四川长虹电器股份有限公司 | Picture upload method based on AWS micro services |
| CN109995713A (en) * | 2017-12-30 | 2019-07-09 | 华为技术有限公司 | Service processing method and relevant device in a kind of micro services frame |
| CN108833137A (en) * | 2018-05-18 | 2018-11-16 | 南京南瑞信息通信科技有限公司 | A kind of flexibility micro services Monitoring framework framework |
| CN108834177A (en) * | 2018-06-08 | 2018-11-16 | 京信通信系统（中国）有限公司 | Load-balancing method, device, computer equipment and storage medium |
| CN108920133A (en) * | 2018-06-14 | 2018-11-30 | 北京三快在线科技有限公司 | Across Programming with Pascal Language method, apparatus, electronic equipment and storage medium |
| CN109089163A (en) * | 2018-07-27 | 2018-12-25 | 武汉斗鱼网络科技有限公司 | Barrage message distributing method, device, equipment and storage medium |
| CN109660585A (en) * | 2018-09-28 | 2019-04-19 | 深圳壹账通智能科技有限公司 | Call method, device, equipment and the storage medium of AOP enhancing objects services |
| CN109587071A (en) * | 2018-11-30 | 2019-04-05 | 北京工业大学 | Micro services load-balancing method based on SDN |
| CN109587246A (en) * | 2018-12-06 | 2019-04-05 | 国云科技股份有限公司 | A kind of implementation method of the micro services frame of integrated multiple kinds independent assortment |
| CN109636334A (en) * | 2018-12-07 | 2019-04-16 | 深圳市汇鑫科技股份有限公司 | A kind of property intelligence community service system and method |
| CN111324577A (en) * | 2018-12-17 | 2020-06-23 | 大唐移动通信设备有限公司 | Method and device for reading and writing Yml file |
| CN109683905A (en) * | 2018-12-24 | 2019-04-26 | 国云科技股份有限公司 | A kind of system method for automatically releasing |
| CN111352577A (en) * | 2018-12-24 | 2020-06-30 | 杭州海康威视系统技术有限公司 | Object storage method and device |
| CN109814909A (en) * | 2019-01-18 | 2019-05-28 | 南京绿新能源研究院有限公司 | Method based on Spring cloud micro services framework cloud SCADA system |
| CN109766080A (en) * | 2019-01-22 | 2019-05-17 | 努比亚技术有限公司 | Micro services register method, device, electronic equipment and readable storage medium storing program for executing |
| CN110048879A (en) * | 2019-03-12 | 2019-07-23 | 平安医疗健康管理股份有限公司 | Micro services register method, device, electronic equipment and computer readable storage medium |
| CN110099099A (en) * | 2019-03-28 | 2019-08-06 | 中国电子科技集团公司电子科学研究院 | For the spatial information micro services encapsulation at terrestrial information port and service integration method |
| CN110149396A (en) * | 2019-05-20 | 2019-08-20 | 华南理工大学 | A kind of platform of internet of things construction method based on micro services framework |
| CN110262972A (en) * | 2019-06-17 | 2019-09-20 | 中国科学院软件研究所 | A kind of failure testing tool and method towards micro services application |
| CN110661780A (en) * | 2019-08-15 | 2020-01-07 | 西安雷迪信息技术有限公司 | Wireless city data sharing method and system based on SAAS application |
| CN110602178A (en) * | 2019-08-26 | 2019-12-20 | 杭州电子科技大学 | Method for calculating and processing temperature sensor data based on edge compression |
| CN110781476A (en) * | 2019-10-15 | 2020-02-11 | 南京南瑞信息通信科技有限公司 | Flexible micro-service security access control method and system |
| CN110971449A (en) * | 2019-10-25 | 2020-04-07 | 武汉烽火众智数字技术有限责任公司 | Service management and control system based on micro-service architecture |
| CN110989983A (en) * | 2019-11-28 | 2020-04-10 | 深圳航天智慧城市系统技术研究院有限公司 | Zero-coding application software rapid construction system |
| CN111193803A (en) * | 2019-12-31 | 2020-05-22 | 四川省公安科研中心 | Spring group-based micro-service construction method and spring group micro-service framework |
| CN111158792A (en) * | 2020-01-02 | 2020-05-15 | 普元信息技术股份有限公司 | System and method for realizing dynamic configurable service parameter verification processing under distributed architecture |
| CN111338813A (en) * | 2020-02-10 | 2020-06-26 | 北京字节跳动网络技术有限公司 | Method, device, medium and electronic equipment for dynamically generating middleware |
| CN111414352A (en) * | 2020-03-27 | 2020-07-14 | 北京明略软件系统有限公司 | Database information management method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112256351A (en) | 2021-01-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109547570B (en) | Service registration method, device, registration center management equipment and storage medium | |
| RU2421785C2 (en) | Automated control of device drivers | |
| US8832679B2 (en) | Registration process for determining compatibility with 32-bit or 64-bit software | |
| US10372463B1 (en) | Provisioning a computerized device with an operating system | |
| US20080222160A1 (en) | Method and system for providing a program for execution without requiring installation | |
| CN101571809A (en) | Implementation method of plug-in registration and device thereof | |
| US7440971B2 (en) | Context based access of files by file system to a client based on detection of related files opened by the client | |
| CN110968331B (en) | Method and device for running application program | |
| CN112256351B (en) | Method for realizing Feign component, method and device for calling micro-service | |
| CN110908753B (en) | Intelligent fusion cloud desktop server, client and system | |
| KR100936239B1 (en) | System And Method For Providing Portable SW With Streaming | |
| CN107220074B (en) | Method and device for accessing and upgrading supporting layer software function | |
| US20240111549A1 (en) | Method and apparatus for constructing android running environment | |
| KR20030084886A (en) | Dynamically downloading and executing system services on a wireless device | |
| CN112073448A (en) | Service isolation method and device for dual-system terminal | |
| US20190196846A1 (en) | Information processing system, container management apparatus, and container management method | |
| US8904396B2 (en) | System and method of general service management | |
| CN114328097A (en) | File monitoring method and device, electronic equipment and storage medium | |
| CN110730197A (en) | Service discovery method and system | |
| CN107783837B (en) | Method and device for performing storage expansion and electronic equipment | |
| CN111683145B (en) | Configuration method of client device, electronic device and medium | |
| JP4063573B2 (en) | Device driver installation / execution method, installation / execution method, and program | |
| CN114356456A (en) | Service processing method, device, storage medium and electronic equipment | |
| CN114816445A (en) | System platform architecture, function publishing method and device, platform and storage medium | |
| CN112860398A (en) | Data processing method, device, equipment and medium based on rule engine |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |