A method, apparatus, electronic device, and storage medium for updating attributes

Abstract

The present application provides a method, apparatus, electronic device, and storage medium for updating attributes. The method includes: adding an update annotation to an instance object that needs to change attribute configurations, and generating an instance object to be updated; wherein the update annotation includes attribute configuration information to be changed, and the instance object is stored in a container; obtaining the instance object to be updated, and obtaining a target object that needs to change attribute configurations from the instance object to be updated; reading an attribute configuration value according to the attribute configuration information in the update annotation; and updating the attribute value of the target object according to the attribute configuration value. Only the instance object with the update annotation added needs to be updated, minimizing the scope of influence of the updated attribute configuration; after updating the configuration information, there is no need to restart the service, increasing the service availability time, reducing the service failure rate, and at the same time reducing the failure cost caused by restarting.

Description

Technical Field

[0001] This application relates to the field of service architectures. Specifically, it relates to a method, device, electronic device, and storage medium for updating attributes. Background Art

[0002] Feign is a declarative service call framework under the microservices architecture and is widely used in the spring cloud system. Due to its convenience, Feign is widely used in scenarios of calling third-party services. Currently, when the configuration information of the Feign client service needs to be changed, the corresponding service needs to be restarted, which has a great impact on the corresponding service after the configuration is changed, with a high service failure rate, resulting in system instability, request exceptions, etc. Summary of the Invention

[0003] The purpose of the embodiments of the present invention is to provide a method, device, electronic device, and storage medium for updating attributes. By adding an update annotation to the instance object whose attributes need to be changed, where the update annotation includes attribute configuration information, obtaining the target object whose attributes need to be changed from the instance object according to the update annotation, reading the attribute configuration value according to the attribute configuration information, and updating the attribute value of the target object according to the attribute configuration value. Among them, only the instance objects with the update annotation added will be updated, minimizing the scope of influence of the updated attribute configuration, and avoiding the problem in the prior art that the corresponding service needs to be restarted when changing the attribute configuration, thereby avoiding request exceptions during the restart process and improving the stability of the system.

[0004] In a first aspect, an embodiment of the present application provides a method for updating attributes, including: adding an update annotation to an instance object whose attribute configuration needs to be changed, and generating an instance object to be updated; where the update annotation includes the attribute configuration information that needs to be changed, and the instance object is stored in a container; obtaining the instance object to be updated, and obtaining the target object whose attribute configuration needs to be changed from the instance object to be updated; reading the attribute configuration value according to the attribute configuration information in the update annotation; and updating the attribute value of the target object according to the attribute configuration value.

[0005] In the above implementation process, an update annotation is added to the instance object whose attribute configuration needs to be changed to obtain the instance object to be updated, the target object is obtained from the instance object to be updated, the attribute configuration value is obtained from the update annotation, and the attribute value of the target object is updated according to the attribute configuration value. Only the instance objects with the update annotation added need to be updated, minimizing the scope of influence of the updated attribute configuration; after updating the configuration information, there is no need to restart the service, increasing the service availability time, reducing the service failure rate, and at the same time reducing the failure cost caused by restarting.

[0006] Optionally, in the embodiments of the present application, adding an update annotation to an instance object whose attribute configuration needs to be changed includes: identifying the instance object whose attribute needs to be changed by adding an update annotation, and the attribute configuration information includes an attribute configuration key and an instance object name. In the above implementation process, the instance object whose attribute configuration needs to be changed is identified by adding an update annotation. There can be many items for updating the attribute configuration. The attribute configuration information value is added to the update annotation. After the instance object with the update annotation is launched again next time, it dynamically modifies the attribute configuration that needs to be modified according to the attribute configuration value. Only the instance object with the update annotation needs to be updated, minimizing the impact scope of updating the attribute configuration.

[0007] Optionally, in the embodiments of the present application, obtaining an instance object to be updated includes: registering a listener in a container, where the listener is used to obtain configuration change information of the instance object, and the configuration change information includes an update annotation of the instance object. The listener obtains the instance object to be updated according to the update annotation of the instance object. In the above implementation process, the listener is registered in the container storing the instance object. When the instance object in the container changes, the listener can obtain the change event of the current container and obtain the instance object whose configuration needs to be changed through the annotation method.

[0008] Optionally, in the embodiments of the present application, the listener obtains the instance object to be updated according to the update annotation of the instance object, including: the listener obtains the instance object to be updated according to the update annotation through the container context environment. In the above implementation process, the listener registered in the container can obtain the instance object with the update annotation through the context or the container.

[0009] Optionally, in the embodiments of the present application, obtaining the instance object to be updated and obtaining a target object whose attribute configuration needs to be changed from the instance object to be updated includes: obtaining the target object from the container storing the instance object to be updated through reflection.

[0010] Optionally, in the embodiments of the present application, updating the attribute value of the target object according to the attribute configuration value includes: updating the attribute value of the target object according to the attribute configuration value through a reflection method.

[0011] Optionally, in the embodiments of the present application, the process of updating an attribute is a single-threaded operation. In the above implementation process, the process of updating the attribute configuration is a single-threaded operation, improving the security between threads.

[0012] In a second aspect, an embodiment of the present application further provides an attribute updating device, including: an annotation adding module, configured to add an update annotation to an instance object whose attribute configuration needs to be changed, and generate an instance object to be updated; wherein, the update annotation includes attribute configuration information that needs to be changed, and the instance object is stored in a container; an object obtaining module, configured to obtain the instance object to be updated, and obtain a target object whose attribute configuration needs to be changed from the instance object to be updated; a reading module, configured to read an attribute configuration value according to the attribute configuration information in the update annotation; and an updating module, configured to update the attribute value of the target object according to the attribute configuration value.

[0013] Optionally, in an embodiment of the present application, the annotation adding module is further configured to identify an instance object whose attribute needs to be changed by adding an update annotation, and the attribute configuration information includes an attribute configuration key and an instance object name.

[0014] Optionally, in an embodiment of the present application, the object obtaining module further includes a listener unit; the listener unit is configured to register a listener in the container, wherein the listener is used to obtain configuration change information of the instance object, and the configuration change information includes an update annotation of the instance object; the listener obtains the instance object to be updated according to the update annotation of the instance object.

[0015] Optionally, in an embodiment of the present application, the listener unit is further configured to obtain the instance object to be updated according to the update annotation through a container context environment.

[0016] Optionally, in an embodiment of the present application, the object obtaining module is further configured to obtain the target object from the container storing the instance object to be updated through reflection.

[0017] Optionally, in an embodiment of the present application, the updating module is further configured to update the attribute value of the target object according to the attribute configuration value through a reflection method.

[0018] Optionally, in an embodiment of the present application, the attribute updating device further includes: a thread module, configured to perform single-threaded operations for updating attributes.

[0019] In a third aspect, an embodiment of the present application further provides an electronic device, including: a processor and a memory, the memory stores machine-readable instructions executable by the processor, and when the machine-readable instructions are executed by the processor, the methods described above are executed.

[0020] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is run by a processor, the methods described above are executed.

[0021] By using the method, apparatus, electronic device, and storage medium for updating attributes provided in this application, only the instance objects with update annotations added will be updated, minimizing the scope affected by the update attribute configuration and avoiding the problem in the prior art that the corresponding service needs to be restarted when changing the attribute configuration, thereby avoiding request exceptions during the restart process and improving the stability of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] To more clearly illustrate the technical solutions of the embodiments of this application, the following briefly introduces the drawings required for use in the embodiments of this application. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as limiting the scope. For those of ordinary skill in the art, without creative efforts, other related drawings can also be obtained based on these drawings.

[0023] Figure 1 A flowchart of a method for updating attributes provided by an embodiment of this application;

[0024] Figure 2 A flowchart of a method for updating the uniform resource locator attribute by a Feign client provided by an embodiment of this application;

[0025] Figure 3 A structural diagram of an apparatus for updating attributes provided by an embodiment of this application; and

[0026] Figure 4 A structural diagram of an electronic device provided by an embodiment of this application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0027] The following will describe in detail the embodiments of the technical solutions of this application in conjunction with the drawings. The following embodiments are only used to more clearly illustrate the technical solutions of this application and thus are only examples and should not be used to limit the protection scope of this application.

[0028] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those of ordinary skill in the technical field to which this application belongs; the terms used herein are only for the purpose of describing specific embodiments and are not intended to limit this application.

[0029] In the description of the embodiments of this application, technical terms such as "first" and "second" are only used to distinguish different objects and cannot be understood as indicating or implying relative importance or implicitly specifying the quantity, specific order, or primary-secondary relationship of the indicated technical features. In the description of the embodiments of this application, "a plurality" means more than two unless otherwise specifically defined.

[0030] Before introducing the attribute updating method provided in the embodiment of the present application, some concepts involved in the embodiment of the present application are first introduced:

[0031] Feign is a lightweight client framework for HTTP requests. It initiates HTTP request calls by annotating interfaces and programming for interfaces, rather than directly calling by encapsulating HTTP request messages like in Java. The service consumer gets the interface of the service provider and then calls it like calling a local interface method, but actually sends a remote request. It is more convenient to call HTTP-based APIs and is widely used in Spring Cloud solutions.

[0032] Spring Cloud is an ordered collection of frameworks. It uses the development convenience of Spring Boot to cleverly simplify the development of distributed system infrastructure, such as service discovery registration, configuration center, message bus, load balancing, circuit breaker, data monitoring, etc., which can all be started and deployed with one click using the Spring Boot development style. See Figure 1 A flowchart of a method for updating attributes provided in an embodiment of the present application is shown.

[0033] Step S110: adding an update annotation to the instance object whose attribute configuration needs to be changed, and generating an instance object to be updated; wherein the update annotation includes the attribute configuration information that needs to be changed, and the instance object is stored in a container.

[0034] The implementation method of the above step S110 includes: adding an update annotation to the instance object whose property configuration needs to be changed, and generating an instance object to be updated, wherein the update annotation includes the property configuration information that needs to be changed, and the instance object is stored in a container. Specifically, the instance object can be a bean in a spring container.

[0035] In a preferred embodiment, this solution can be used to change the property configuration of the Feign client, and the changed property configuration includes but is not limited to the uniform resource locator and timeout period. The Feign client exists in the Spring container in the form of a singleton bean in Spring. The bean whose properties need to be changed is identified by adding an update annotation. Specifically, an update annotation is added to the Feign client interface whose property configuration needs to be changed. The update annotation can be @PrepareLaunchClient, and the property configuration information that needs to be changed is configured in the update annotation. For example, when the uniform resource locator needs to be changed, the key of the URL that needs to be changed is configured in the annotation.

[0036] After step S110, step S120 is executed: obtaining the instance object to be updated, and obtaining the target object whose attribute configuration needs to be changed from the instance object to be updated.

[0037] The implementation method of the above step S120 includes: the instance object to be updated is an instance object to which an update annotation has been added. By adding a listener with attribute configuration, when the instance object in the container changes, the instance object to which the update annotation has been added can be obtained from the container. For example, a Feign client to which the @PrepareLaunchClient annotation has been added is obtained from the spring container.

[0038] After step S120, step S130 is executed: according to the attribute configuration information in the update annotation, the attribute configuration value is read.

[0039] The implementation of the above step S130 includes: reading the attribute configuration value in the attribute configuration information, for example, reading the value corresponding to the key where the URL to be changed is located configured in the update annotation.

[0040] After step S130, step S140 is executed: updating the attribute value of the target object according to the attribute configuration value.

[0041] The implementation method of the above step S140 includes: updating the attribute value of the target object according to the attribute configuration value, for example, modifying the URL in the Feign client, and the modified value is the value corresponding to the key where the URL is identified in the @PrepareLaunchClient annotation.

[0042] It should be noted that after the listener updates the URL attribute value in the Feign client, other requests initiate calls to the Feign client again, using the updated URL value.

[0043] In the above implementation process, an update annotation is added to the instance object whose attribute configuration needs to be changed, the instance object to be updated is obtained, the target object is obtained from the instance object to be updated, the attribute configuration value is obtained in the update annotation, and the attribute value of the target object is updated according to the attribute configuration value. Only the instance object with the update annotation added needs to be updated, which minimizes the impact of updating the attribute configuration; after updating the configuration information, there is no need to restart the service, which increases the service availability time, reduces the service failure rate, and reduces the failure cost caused by restart.

[0044] Optionally, in an embodiment of the present application, adding an update annotation to an instance object whose attribute configuration needs to be changed includes: identifying the instance object whose attribute needs to be changed by adding an update annotation, and the attribute configuration information includes an attribute configuration key and an instance object name.

[0045] Embodiments of the above steps are as follows: For example, identify the instance objects whose attributes need to be changed by adding update annotations, that is, only add update annotations to the instance objects whose configurations need to be changed. When updating the attribute configuration, only update the instance objects with update annotations added. In the above implementation process, the Feign client attribute configuration is updated in real time, and the instance objects that need to update the configuration are marked by adding update annotations, avoiding restarting the service for updating the attribute configuration and minimizing the impact of updating the attribute configuration.

[0046] Optionally, in an embodiment of the present application, obtaining the instance object to be updated includes: registering a listener in the container, where the listener is used to obtain the configuration change information of the instance object, and the configuration change information includes the update annotation of the instance object. The listener obtains the instance object to be updated according to the update annotation of the instance object.

[0047] Embodiments of the above steps are as follows: Register a listener in the container. If the attribute configuration in the container changes, the listener obtains the change information, which is the attribute configuration information that needs to be changed, and obtains the instance object to be updated with an update annotation added from the container. In a preferred embodiment, add the listener as a watcher for the property configuration of the current zookeeper application. When the property configuration changes, zookeeper sends the property configuration change information to the listener. The property configuration change information includes the value of the property configuration that needs to be changed. After the listener obtains the change information, it obtains the instance object to be updated with an update annotation added from the container.

[0048] Optionally, in an embodiment of the present application, where the listener obtains the instance object to be updated according to the update annotation of the instance object includes: the listener obtains the instance object to be updated according to the update annotation through the container context environment.

[0049] Embodiments of the above steps are as follows: When the listener obtains the change information of the container, it can obtain the instance object to be updated with an update annotation added through the container. Specifically, for example, the listener registered in the Spring container obtains the instance object to be updated with an update annotation added through the ApplicationContext in Spring or through the getBeansWithAnnotation(Class annotationType) method provided by the Spring container BeanFactory.

[0050] Optionally, in an embodiment of the present application, obtaining the instance object to be updated and obtaining the target object whose attribute configuration needs to be changed from the instance object to be updated includes: obtaining the target object from the container storing the instance object to be updated through reflection.

[0051] For example, the implementation of the above steps is as follows: update the Feign client property configuration, obtain the Feign client proxy object from the Spring container storing the entity object to be updated, and obtain the target object through reflection based on the Feign client proxy object.

[0052] Optionally, in the embodiment of the present application, updating the attribute value of the target object according to the attribute configuration value includes: updating the attribute value of the target object according to the attribute configuration value through reflection.

[0053] Optionally, in the embodiment of the present application, the process of updating attributes is a single-threaded operation. In the above implementation process, the process of updating attribute configuration is a single-threaded operation, which improves the security between threads.

[0054] Please refer to Figure 2 the schematic flowchart of the method for updating the uniform resource locator attribute of the Feign client provided by the embodiment of the present application shown;

[0055] In a preferred embodiment, the method for updating attributes provided by the present application can be applied to the Feign client. As Figure 2 shown, update the path attribute of the Feign client. The Feign client is stored in the Spring container in the form of a singleton bean in Spring. Add the update annotation @PrepareLaunchClient to the Feign client interface that needs to change the path, and configure the attribute configuration information that needs to be changed in this update annotation, that is, the path configuration information that needs to be changed;

[0056] The listener adds itself as a watcher for the configuration path of the current application of Zookeeper. When the configuration path changes, Zookeeper will send path change information to the listener. Therefore, the listener monitors that the Zookeeper path configuration has changed;

[0057] The listener obtains the proxy object of the bean with the update annotation added from the Spring container;

[0058] Obtain the value of the path configuration information that needs to be changed in the update annotation through reflection. For example, "URL" = "user.url", and read the updated value of "user.url" from the path configuration information;

[0059] Obtain the target object from the proxy object. Here, the target object is obtained from the proxy object of the bean, which is the Feign client that needs to change the path attribute;

[0060] Configure the path attribute of the target object to the updated value of "user.url";

[0061] After the target object, that is, the Feign client path value that needs to change the path attribute, is updated successfully, other requests will initiate a call to the Feign client again, using the updated path value.

[0062] In the above implementation process, an update annotation is added to the instance object whose property configuration needs to be changed, the proxy object of the bean with the update annotation is obtained, the target object is obtained from the proxy object of the bean with the update annotation, the property configuration value is obtained in the update annotation, and the property value of the target object is updated according to the property configuration value. Only the target object needs to be selected from the proxy object of the bean with the update annotation for update, which minimizes the impact of the updated property configuration. And there is no need to restart the service after updating the configuration information, so that the updated target object can be used again directly, thereby increasing the service availability time, reducing the service failure rate, and reducing the failure cost caused by restart.

[0063] See also Figure 3 The structure diagram of the device for updating attributes provided by the embodiment of the present application is shown; the embodiment of the present application provides an updating attribute 200, including:

[0064] An annotation adding module 210 is used to add an update annotation to an instance object whose attribute configuration needs to be changed, and generate an instance object to be updated; wherein the update annotation includes the attribute configuration information that needs to be changed, and the instance object is stored in a container;

[0065] The object acquisition module 220 is used to acquire the instance object to be updated, and acquire the target object whose attribute configuration needs to be changed from the instance object to be updated;

[0066] A reading module 230, configured to read attribute configuration values ​​according to the attribute configuration information in the update annotation; and

[0067] The updating module 240 is used to update the attribute value of the target object according to the attribute configuration value.

[0068] It should be understood that the device corresponds to the above-mentioned server routing method embodiment and can execute the various steps involved in the above-mentioned method embodiment. The specific functions of the device can be found in the description above. To avoid repetition, the detailed description is appropriately omitted here. The device includes at least one software function module that can be stored in a memory in the form of software or firmware or solidified in the operating system (OS) of the device.

[0069] See also Figure 4Schematic structural diagram of the electronic device provided by the embodiment of the present application. An electronic device 300 provided by the embodiment of the present application includes: a processor 310 and a memory 320. The memory 320 stores machine-readable instructions executable by the processor 310. When the machine-readable instructions are executed by the processor 310, the above method is executed.

[0070] The embodiment of the present application also provides a storage medium. A computer program is stored on the storage medium. When the computer program is run by a processor, the above method is executed.

[0071] Among them, the storage medium can be implemented by any physical object type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (abbreviated as SRAM), electrically erasable programmable read-only memory (abbreviated as EEPROM), erasable programmable read-only memory (abbreviated as EPROM), programmable read-only memory (abbreviated as PROM), read-only memory (abbreviated as ROM), magnetic memory, flash memory, magnetic disk or optical disc.

[0072] In several embodiments provided by the embodiment of the present application, it should be understood that the disclosed device and method can also be implemented in other ways. The device embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the drawings show the possible architectures, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present application. In this regard, each block in the flowchart or block diagram may represent a module, a program segment, or a part of code. The module, program segment, or part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order from that marked in the drawings. For example, two consecutive blocks can actually be executed substantially in parallel, and they can sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and the combination of blocks in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0073] In addition, in each embodiment of the present application, each functional module can be integrated together to form an independent part, or each module can exist alone, or two or more modules can be integrated to form an independent part.

[0074] The above description is only an optional implementation manner of the embodiments of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the embodiments of the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the embodiments of the present application.

Claims

1. A method for updating attributes, characterized in that, Including: Adding an update annotation to the instance object that needs to change the attribute configuration, and generating an instance object to be updated; wherein, the update annotation includes the attribute configuration information to be changed, and the instance object is stored in a container; the attribute configuration information to be changed includes the uniform resource locator and timeout of the Feign client; Obtaining the instance object to be updated, and obtaining the target object that needs to change the attribute configuration from the instance object to be updated; Reading the attribute configuration value according to the attribute configuration information in the update annotation; and Updating the attribute value of the target object according to the attribute configuration value; the attribute value is the value corresponding to the key where the uniform resource locator is located; Wherein, obtaining the instance object to be updated includes: registering a listener into the container, wherein the listener is used to obtain the configuration change information of the instance object, and the configuration change information includes the update annotation of the instance object; the listener obtains the instance object to be updated according to the update annotation of the instance object; The listener obtaining the instance object to be updated according to the update annotation of the instance object includes: the listener obtaining the instance object to be updated according to the update annotation through the container context environment.

2. The method according to claim 1, characterized in that, Wherein, Adding an update annotation to the instance object that needs to change the attribute configuration includes: Identifying the instance object that needs to change the attribute by adding an update annotation, and the attribute configuration information includes an attribute configuration key and an instance object name.

3. The method according to claim 1, characterized in that, Wherein, Obtaining the instance object to be updated, and obtaining the target object that needs to change the attribute configuration from the instance object to be updated includes: Obtaining the target object from the container storing the instance object to be updated through reflection.

4. The method according to claim 1, characterized in that, Wherein, Updating the attribute value of the target object according to the attribute configuration value includes: Updating the attribute value of the target object according to the attribute configuration value through a reflection method.

5. The method according to claim 1, characterized in that, Wherein, The process of updating the attribute is a single-threaded operation.

6. An apparatus for updating attributes, characterized in that, Including: An annotation adding module, which is used to add an update annotation to the instance object that needs to change the attribute configuration, and generate an instance object to be updated; wherein, the update annotation includes the attribute configuration information to be changed, and the instance object is stored in a container; the attribute configuration information to be changed includes the uniform resource locator and timeout of the Feign client; An object obtaining module, which is used to obtain the instance object to be updated, and obtain the target object that needs to change the attribute configuration from the instance object to be updated; A reading module, which is used to read the attribute configuration value according to the attribute configuration information in the update annotation; and An updating module, which is used to update the attribute value of the target object according to the attribute configuration value; the attribute value is the value corresponding to the key where the uniform resource locator is located; The object obtaining module is used to register a listener into the container, wherein the listener is used to obtain the configuration change information of the instance object, and the configuration change information includes the update annotation of the instance object; the listener obtains the instance object to be updated according to the update annotation of the instance object; The object acquisition module is specifically configured to obtain the instance object to be updated by the listener according to the update annotation through the container context environment.

7. An electronic device, characterized in that, It includes: a processor and a memory, where the memory stores machine-readable instructions executable by the processor, and when the machine-readable instructions are executed by the processor, the method according to any one of claims 1 to 4 is executed.

8. A computer-readable storage medium, characterized in that, A computer program is stored on the computer-readable storage medium, and when the computer program is run by a processor, the method according to any one of claims 1 to 4 is executed.

Images