Spring Boot framework-based configuration management method and apparatus, and electronic device
By implementing dynamic updates and encryption/decryption of configurations within the Spring Boot framework through a custom configuration framework, the complexity of Spring Cloud Config is resolved, configuration management is simplified, and costs are reduced.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-01-04
- Publication Date
- 2026-04-14
AI Technical Summary
Spring Cloud Config's configuration refresh mechanism is complex, requiring additional Spring Cloud Bus components or manual triggering of the Refresh endpoint, which increases system complexity and enterprise development and usage costs.
Create a custom configuration framework, including configuration management classes, configuration refresh classes, configuration attribute location classes, and framework configuration guidance classes. It supports JNDI data sources and direct data sources, enabling dynamic updates and flexible encryption/decryption of configurations. The custom configuration framework automatically loads configuration tables and detects configuration changes.
It enables dynamic updates and flexible encryption/decryption of configurations without the need for server configuration, simplifying configuration management complexity, reducing development and usage costs, and adapting to different deployment environments.
Smart Images
Figure CN121858152A_ABST
Abstract
Description
Technical Field
[0001] This application relates primarily to the field of computer software technology, and in particular to a configuration management method, apparatus, and electronic device based on the Spring Boot framework. Background Technology
[0002] In the Spring Boot framework, the Spring Cloud Config configuration server enables centralized management of configuration files for all applications. However, the Spring Cloud Config configuration refresh mechanism is complex, requiring additional Spring Cloud Bus components or manual triggering of the Refresh endpoint to refresh the configuration. Furthermore, the independent deployment of the configuration server increases system complexity, thereby impacting the development and usage costs for enterprises. Summary of the Invention
[0003] The purpose of this disclosure is to provide a configuration management method, device, and electronic device based on the Spring Boot framework, which can realize dynamic updates of configuration and flexible encryption and decryption mechanisms without the need for a configuration server, simplifying the complexity of configuration management and reducing development and usage costs.
[0004] Firstly, this application provides a configuration management method based on the Spring Boot framework, including: Create a custom configuration framework, which includes: a configuration management class, a configuration refresh class, a configuration attribute locator class, and a framework configuration guide class. The configuration management class is used to initialize the custom data source connection, query the configuration from the custom data source, and is responsible for the encryption and decryption mechanism. The configuration refresh class is used to listen for application startup events, periodically check for configuration changes, and publish a configuration refresh event when the configuration changes. The configuration attribute locator class is used to extend the loading logic of the custom data source. The framework configuration guide class is used to implement the automatic assembly of the custom configuration framework. Include all dependencies of the custom configuration framework in the pom.xml file of the original Spring Boot framework-based project; Create a configuration table for the project in the custom data source, and configure the relevant connection information of the custom data source in the configuration file applied in the project; When the application starts, the configuration table in the custom data source is automatically loaded through the custom configuration framework.
[0005] In one alternative implementation, the custom data source includes a JNDI data source and a direct-connect data source.
[0006] In one optional implementation, the relevant connection information includes the database driver class name, database type, connection address, authentication information, and configuration table query SQL.
[0007] In one alternative implementation, it further includes: Create and use a configuration utility class to generate an RSA key pair, and use the private key in the RSA key pair to encrypt the sensitive configuration in the configuration table to obtain the encrypted configuration; Configure the public key of the RSA key pair in the application's configuration file, and store the encryption configuration in the custom data source. The encryption configuration has a custom encryption prefix.
[0008] In one alternative implementation, it further includes: Update the configuration value in the configuration table; When the configuration refresh event is triggered, the configuration items associated with the configuration value in the application's Spring container are automatically updated through the custom configuration framework.
[0009] Secondly, this application provides a configuration management device based on the Spring Boot framework, comprising: A custom configuration framework creation module is used to create a custom configuration framework. The custom configuration framework includes: a configuration management class, a configuration refresh class, a configuration attribute locator class, and a framework configuration guide class. The configuration management class is used to initialize the custom data source connection, query the configuration from the custom data source, and is responsible for the encryption and decryption mechanism. The configuration refresh class is used to listen for application startup events, periodically check for configuration changes, and publish a configuration refresh event when the configuration changes. The configuration attribute locator class is used to extend the loading logic of the custom data source. The framework configuration guide class is used to implement the automatic assembly of the custom configuration framework. The dependency import module is used to import all dependencies of the custom configuration framework into the pom.xml file of the original Spring Boot framework-based project; The connection information configuration module is used to create a configuration table for the project in the custom data source and configure the relevant connection information of the custom data source in the configuration file applied in the project. The configuration table loading module is used to automatically load the configuration table in the custom data source through the custom configuration framework when the application starts.
[0010] In one alternative implementation, it further includes: The configuration encryption / decryption module is used to create and use the configuration utility class to generate RSA key pairs, and use the private key in the RSA key pair to encrypt the sensitive configuration in the configuration table to obtain the encrypted configuration; An encrypted configuration storage module is used to configure the public key in the RSA key pair in the application's configuration file and store the encrypted configuration in the custom data source, wherein the encrypted configuration has a custom encryption prefix.
[0011] In one alternative implementation, it further includes: A dynamic update module is configured to update configuration values in the configuration table; and, when the configuration refresh event is triggered, to automatically update the configuration items associated with the configuration values in the application's Spring container through the custom configuration framework.
[0012] Thirdly, an electronic device is provided. The electronic device includes: one or more processors; and one or more memories coupled to the one or more processors and storing instructions thereon. When the instructions are executed individually or jointly by the one or more processors, the electronic device performs the methods described above.
[0013] Fourthly, a non-transitory computer-readable storage medium is provided that stores machine-executable instructions. When executed by one or more processors of a machine, the machine-executable instructions cause the machine to perform any of the methods described above.
[0014] The beneficial effects of the solution provided in this disclosure are as follows: By creating a custom configuration framework and including all its dependencies in the pom.xml file of the original Spring Boot project, a configuration table is created in the custom data source, and the relevant connection information for the custom data source is configured in the application's configuration file. When the application starts, the configuration table in the custom data source is automatically loaded by the custom configuration framework, achieving data source-driven configuration storage. This enables dynamic configuration updates and flexible encryption / decryption mechanisms without requiring a configuration server, simplifying configuration management complexity and reducing development and usage costs. Furthermore, the custom configuration framework can automatically detect configuration changes and publish configuration refresh events without manual triggering. The custom data source supports both JNDI and direct connection data sources, adapting to different deployment environments. Attached Figure Description
[0015] The above and other objects, features, and advantages of this disclosure will become more apparent from the more detailed description of some embodiments thereof in the accompanying drawings, in which: Figure 1 This is a flowchart illustrating a configuration management method based on the Spring Boot framework according to some embodiments of this disclosure; Figure 2This is a schematic diagram of a configuration management device based on the Spring Boot framework according to some embodiments of the present disclosure; Figure 3 This is a simplified block diagram of an electronic device suitable for implementing exemplary embodiments of the present disclosure. Detailed Implementation
[0016] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not impose any limitation on the scope of this disclosure. The disclosure described herein may be implemented in ways other than those described below.
[0017] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.
[0018] References to "an embodiment," "embodiment," "exemplary embodiment," etc., in this disclosure indicate that the described embodiments may include specific features, structures, or characteristics, but not every embodiment needs to include specific features, structures, or characteristics. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, when a specific feature, structure, or characteristic is described in connection with an exemplary embodiment, whether explicitly described or not, those skilled in the art will recognize that such a feature, structure, or characteristic affects its connection to other embodiments.
[0019] It should be understood that while the terms “first” and “second”, etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. The term “and / or” as used herein includes any and all combinations of one or more of the listed terms.
[0020] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. The singular forms “a,” “an,” and “the” used herein also include the plural forms unless the context clearly indicates otherwise. The terms “a group of elements” or “a collection of elements” as used herein are intended to include one or more elements. It should also be understood that the terms “comprising,” “including,” “having,” “possessing,” “including,” and / or “comprising,” when used herein, specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.
[0021] Spring Boot framework: A lightweight and rapid development framework based on the Spring framework.
[0022] JNDI data source: A management method that configures the database connection pool to be hosted on application servers such as Tomcat / JBoss.
[0023] Figure 1 This is a flowchart illustrating a configuration management method based on the Spring Boot framework, according to some embodiments of this disclosure. Figure 1 ,include: S101, Create a custom configuration framework.
[0024] The custom configuration framework includes: configuration management class, configuration refresh class, configuration attribute location class, and framework configuration guidance class.
[0025] The configuration management class (ConfigManager.java) is used to initialize custom data source connections, query configurations from custom data sources, and handle encryption / decryption mechanisms. Optionally, the configuration management class also provides configuration checking and retrieval functionality.
[0026] The configuration refresh class (ConfigRefresher.java) is used to listen for application startup events, periodically check for configuration changes, and publish configuration refresh events when configuration changes occur.
[0027] The configuration property locator class (ConfigPropertySourceLocator.java) is used to extend the loading logic of custom data sources. For example, it implements the Spring Cloud PropertySourceLocator interface to ensure that the configuration can be correctly loaded and used by the Spring container.
[0028] The framework configuration bootstrap classes (FrameworkConfigBootstrapConfigure.java and FrameworkConfigAutoConfigure.java) are used to automate the configuration of custom configuration frameworks. This includes automatically registering components such as the configuration management class, configuration property locator class, and framework configuration bootstrap class; enabling configuration property binding; and ensuring that components are initialized in the correct order.
[0029] S102, import all dependencies of the custom configuration framework into the pom.xml file of the original Spring Boot framework-based project.
[0030] S103, create a configuration table for the project in the custom data source, and configure the relevant connection information of the custom data source in the configuration file applied in the project.
[0031] In one alternative implementation, the custom data source includes a JNDI data source and a direct-connect data source.
[0032] In one optional implementation, the relevant connection information includes the database driver class name, database type, connection address, authentication information, and configuration table query SQL.
[0033] For example, a MySQL relational database managed in a direct connection mode can be used as a custom data source. The format of the relevant connection information in the configuration file is as follows: #Direct connection to data source cpic.tech.framework.config.driver-class-name=com. mysql.jdbc.Driver cpic.tech.framework.config.db-type=mysql cpic.tech.framework.config.url=jdbc:mysql: / / localhost:3306 / config cpic.tech.framework.config.username=root cpic.tech.framework.config.password=root cpic.tech.framework.config.query-sql=SELECT config_key, config_value FROM t_config The format of the project's configuration table is as follows: CREATE TABLE t_config ( config_key VARCHAR(500) PRIMARY KEY, config_value TEXT ) Subsequently, when the application starts, the custom configuration framework can automatically load the configuration table in the custom data source, thereby realizing data source-driven configuration storage.
[0034] S104 automatically loads the configuration table from the custom data source through a custom configuration framework when the application starts.
[0035] In an optional implementation, the method further includes: creating and using a configuration utility class to generate an RSA key pair; encrypting a sensitive configuration in a configuration table using the private key in the RSA key pair to obtain an encrypted configuration; configuring the public key in the RSA key pair in the application's configuration file; and storing the encrypted configuration in a custom data source, wherein the encrypted configuration has a custom encryption prefix.
[0036] For example, ConfigTools can be used to generate RSA key pairs, in the following format: ConfigTools.generateKey(); / / Then, use ConfigTools.encrypt to encrypt sensitive configurations, and configure the public key in the configuration file, in the following format: The public key generated by cpic.tech.framework.config.public-key=... The above methods can provide a flexible encryption and decryption mechanism for configuration management, and allow for custom encryption prefixes to improve configuration security.
[0037] In an alternative implementation, the method further includes: updating the configuration value in the configuration table; and automatically updating the configuration items associated with the configuration value in the application's Spring container via a custom configuration framework when a configuration refresh event is triggered.
[0038] For example, you can directly update the configuration value, in the following format: UPDATE t_config SET config_value = 'newValue' WHERE config_key = 'some.property'; Subsequently, the custom configuration framework can detect configuration changes. When a configuration refresh event is triggered, the framework will automatically update the configuration items associated with the configuration values in the application's Spring container, achieving dynamic configuration updates without restarting the application.
[0039] Based on the above approach, this solution enables dynamic configuration updates and flexible encryption / decryption mechanisms without requiring a dedicated server, simplifying configuration management and reducing development and usage costs. Furthermore, the custom configuration framework can automatically detect configuration changes and publish configuration refresh events without manual triggering. Additionally, the custom data source supports both JNDI and direct connection data sources, adapting to different deployment environments.
[0040] Figure 2This is a schematic diagram of a configuration management device based on the Spring Boot framework, provided according to some embodiments of this disclosure. Figure 2 The device includes: The custom configuration framework creation module 201 is used to create a custom configuration framework. The custom configuration framework includes: a configuration management class, a configuration refresh class, a configuration attribute locator class, and a framework configuration guide class. The configuration management class is used to initialize the custom data source connection, query configuration from the custom data source, and handle configuration encryption and decryption. The configuration refresh class is used to listen for application startup events, periodically check for configuration changes, and publish configuration refresh events when configuration changes occur. The configuration attribute locator class is used to extend the loading logic of the custom data source. The framework configuration guide class is used to implement the automatic assembly of the custom configuration framework.
[0041] Dependency import module 202 is used to import all dependencies of the custom configuration framework into the pom.xml file of the original Spring Boot framework-based project.
[0042] The connection information configuration module 203 is used to create a configuration table for the project in the custom data source and configure the relevant connection information of the custom data source in the configuration file applied in the project.
[0043] Configuration table loading module 204 is used to automatically load configuration tables from a custom data source using a custom configuration framework when the application starts.
[0044] In an optional implementation, the system further includes: a configuration encryption / decryption module 205, used to create and use a configuration utility class to generate an RSA key pair, and use the private key in the RSA key pair to encrypt sensitive configurations in the configuration table to obtain encrypted configurations; and an encrypted configuration storage module 206, used to configure the public key in the RSA key pair in the application's configuration file, and store the encrypted configurations in a custom data source, wherein the encrypted configurations have a custom encryption prefix.
[0045] In an optional implementation, it further includes: a configuration dynamic update module 207 for updating configuration values in a configuration table; and, when a configuration refresh event is triggered, automatically updating the configuration items associated with the configuration values in the application's Spring container through a custom configuration framework.
[0046] An embodiment of this disclosure provides a configuration management device based on the Spring Boot framework. Figure 1 The implementation of a configuration management method based on the Spring Boot framework is shown below. The specific steps and technical effects can be found in the previous descriptions, and will not be repeated here.
[0047] Furthermore, such as Figure 3An exemplary embodiment of this application also provides an electronic device including one or more memories 301 and one or more processors 302, wherein the one or more memories 301 are coupled to and store instructions thereon on the one or more processors 302, the instructions being executable individually or jointly by the one or more processors 302, causing the electronic device to perform the method as described in any of the first aspects.
[0048] It should be understood that the processor mentioned in the embodiments of this application can be a CPU, or other general-purpose processors, DSPs, ASICs, FPGAs, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.
[0049] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory, dynamic random access memory, synchronous dynamic random access memory, double data rate synchronous dynamic random access memory, enhanced synchronous dynamic random access memory, synchronous linked dynamic random access memory, and direct memory bus random access memory.
[0050] This application also provides a non-transitory computer-readable storage medium storing machine-executable instructions that can be executed by one or more processors of a machine. The machine may include electronic devices as mentioned above. When the machine-executable instructions are executed by one or more processors, the machine performs any of the methods mentioned above.
[0051] The basic concepts have been described above. Obviously, for those skilled in the art, the above disclosure is merely illustrative and does not constitute a limitation of this application. Although not explicitly stated herein, those skilled in the art may make various modifications, improvements, and corrections to this application. Such modifications, improvements, and corrections are suggested in this application, and therefore remain within the spirit and scope of the exemplary embodiments of this application.
[0052] Furthermore, this application uses specific terms to describe embodiments of the application. For example, "an embodiment," "one embodiment," and / or "some embodiments" refer to a particular feature, structure, or characteristic related to at least one embodiment of the application. Therefore, it should be emphasized and noted that "an embodiment," "one embodiment," or "an alternative embodiment" mentioned twice or more in different locations in this specification do not necessarily refer to the same embodiment. In addition, certain features, structures, or characteristics in one or more embodiments of the application can be appropriately combined.
[0053] Some aspects of this application can be executed entirely by hardware, entirely by software (including firmware, resident software, microcode, etc.), or by a combination of hardware and software. The aforementioned hardware or software may be referred to as a "data block," "module," "engine," "unit," "component," or "system." The processor may be one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DAPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or combinations thereof. Furthermore, aspects of this application may manifest as computer products residing in one or more computer-readable media, including computer-readable program code. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes, etc.), optical discs (e.g., compressed CDs, digital multifunction DVDs, etc.), smart cards, and flash memory devices (e.g., cards, sticks, key drives, etc.).
[0054] A computer-readable medium may contain a propagated data signal containing computer program code, for example, on baseband or as part of a carrier wave. This propagated signal may take various forms, including electromagnetic, optical, and so on, or suitable combinations thereof. A computer-readable medium can be any computer-readable medium other than a computer-readable storage medium, which can be connected to an instruction execution system, apparatus, or device to enable communication, propagation, or transmission of a program for use. The program code located on the computer-readable medium can be propagated through any suitable medium, including radio, cable, fiber optic cable, radio frequency signals, or similar media, or any combination of the above media.
[0055] Similarly, it should be noted that, in order to simplify the description of the present application and thus aid in the understanding of one or more embodiments of the invention, the foregoing description of the embodiments of the present application sometimes combines multiple features into a single embodiment, drawing, or description thereof. However, this disclosure method does not imply that the subject matter of the application requires more features than those mentioned in the claims. In fact, the embodiments contain fewer features than all the features of the single embodiments disclosed above.
[0056] In some embodiments, numbers describing the quantity of components and attributes are used. It should be understood that such numbers used in the description of embodiments are modified in some examples with the terms "approximately," "approximately," or "generally." Unless otherwise stated, "approximately," "approximately," or "generally" indicates that the numbers are allowed to vary by ±20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximate values, which may be changed depending on the characteristics required by individual embodiments. In some embodiments, numerical parameters should take into account specified significant digits and employ a general method of digit reservation. Although the numerical ranges and parameters used to confirm their breadth of scope in some embodiments of this application are approximate values, in specific embodiments, such values are set as precisely as feasible.
[0057] Although this application has been described with reference to specific embodiments, those skilled in the art should recognize that the above embodiments are only used to illustrate this application, and various equivalent changes or substitutions can be made without departing from the spirit of this application. Therefore, any changes or modifications to the above embodiments within the essential spirit of this application will fall within the scope of the claims of this application.
Claims
1. A configuration management method based on the Spring Boot framework, characterized in that, include: Create a custom configuration framework, which includes: a configuration management class, a configuration refresh class, a configuration attribute locator class, and a framework configuration guide class. The configuration management class is used to initialize the custom data source connection, query the configuration from the custom data source, and is responsible for the encryption and decryption mechanism. The configuration refresh class is used to listen for application startup events, periodically check for configuration changes, and publish a configuration refresh event when the configuration changes. The configuration attribute locator class is used to extend the loading logic of the custom data source. The framework configuration guide class is used to implement the automatic assembly of the custom configuration framework. Include all dependencies of the custom configuration framework in the pom.xml file of the original Spring Boot framework-based project; Create a configuration table for the project in the custom data source, and configure the relevant connection information of the custom data source in the configuration file applied in the project; When the application starts, the configuration table in the custom data source is automatically loaded through the custom configuration framework.
2. The method as described in claim 1, characterized in that, The custom data source includes JNDI data source and direct connection data source.
3. The method as described in claim 2, characterized in that, The relevant connection information includes the database driver class name, database type, connection address, authentication information, and configuration table query SQL.
4. The method as described in claim 1, characterized in that, Also includes: Create and use a configuration utility class to generate an RSA key pair, and use the private key in the RSA key pair to encrypt the sensitive configuration in the configuration table to obtain the encrypted configuration; Configure the public key of the RSA key pair in the application's configuration file, and store the encryption configuration in the custom data source. The encryption configuration has a custom encryption prefix.
5. The method as described in claim 1, characterized in that, Also includes: Update the configuration value in the configuration table; When the configuration refresh event is triggered, the configuration items associated with the configuration value in the application's Spring container are automatically updated through the custom configuration framework.
6. A configuration management device based on the Spring Boot framework, characterized in that, include: A custom configuration framework creation module is used to create a custom configuration framework. The custom configuration framework includes: a configuration management class, a configuration refresh class, a configuration attribute locator class, and a framework configuration guide class. The configuration management class is used to initialize the custom data source connection, query the configuration from the custom data source, and is responsible for the encryption and decryption mechanism. The configuration refresh class is used to listen for application startup events, periodically check for configuration changes, and publish a configuration refresh event when the configuration changes. The configuration attribute locator class is used to extend the loading logic of the custom data source. The framework configuration guide class is used to implement the automatic assembly of the custom configuration framework. The dependency import module is used to import all dependencies of the custom configuration framework into the pom.xml file of the original Spring Boot framework-based project; The connection information configuration module is used to create a configuration table for the project in the custom data source and configure the relevant connection information of the custom data source in the configuration file applied in the project. The configuration table loading module is used to automatically load the configuration table in the custom data source through the custom configuration framework when the application starts.
7. The apparatus as claimed in claim 6, characterized in that, Also includes: The configuration encryption / decryption module is used to create and use the configuration utility class to generate RSA key pairs, and use the private key in the RSA key pair to encrypt the sensitive configuration in the configuration table to obtain the encrypted configuration; An encrypted configuration storage module is used to configure the public key in the RSA key pair in the application's configuration file and store the encrypted configuration in the custom data source, wherein the encrypted configuration has a custom encryption prefix.
8. The apparatus as claimed in claim 6, characterized in that, Also includes: A dynamic update module is configured to update configuration values in the configuration table; and, when the configuration refresh event is triggered, to automatically update the configuration items associated with the configuration values in the application's Spring container through the custom configuration framework.
9. An electronic device, characterized in that, include: One or more processors; And one or more memories coupled to the one or more processors and storing instructions thereon; When the instructions are executed individually or jointly by the one or more processors, the electronic device performs the method as described in any one of claims 1-5.
10. A non-transitory computer-readable storage medium storing machine-executable instructions, characterized in that, When the machine-executable instructions are executed by one or more processors of the machine, the machine performs the method as described in any one of claims 1-5.