CN111131472A - Building method of Apollo configuration center - Google Patents
Building method of Apollo configuration center Download PDFInfo
- Publication number
- CN111131472A CN111131472A CN201911378664.0A CN201911378664A CN111131472A CN 111131472 A CN111131472 A CN 111131472A CN 201911378664 A CN201911378664 A CN 201911378664A CN 111131472 A CN111131472 A CN 111131472A
- Authority
- CN
- China
- Prior art keywords
- service
- apollo
- configuration
- database
- adminservice
- 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.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
- H04L67/145—Termination or inactivation of sessions, e.g. event-controlled end of session avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Computing Systems (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a building method of an Apollo configuration center, which comprises the following steps: creating a ConfigDB database and a PortalDB database and finishing initialization; downloading and installing a Configservice service, an adminService service and a Portal service; and respectively deploying Configservice service, Adminservice and Portal service. The method can be obtained in real time after configuration modification, and projects do not need to be restarted; and can uniformly maintain the configuration files of all projects.
Description
Technical Field
The invention relates to the field of information technology processing, in particular to a building method of an Apollo configuration center.
Background
With the increasing complexity of program functions and the increasing configuration of programs in a distributed system, the configuration of switches, parameters, addresses of servers and the like of various functions is complicated, the expected value of the program configuration is higher, the configuration is effective in real time after being modified, the gray scale is released, the management configuration of sub-environments and diversity groups, and the conventional permission and audit mechanism … … cannot meet the requirements of developers on the configuration management more and more through configuration files, databases and the like in such a large environment. Therefore, there is a need for unified configuration management of services in a distributed system, thereby improving the simplicity and usability of the system.
Apollo (Apollo) is a distributed configuration center developed by a portable framework department, can be used for centralized management of configurations of different environments and different clusters, can be pushed to an application end in real time after configuration modification, has the characteristics of standard authority, process management and the like, and is suitable for a micro-service configuration management scene. However, the conventional Apollo configuration is complex, and project access is difficult to operate.
Disclosure of Invention
In view of this, the present invention provides a method for building an Apollo configuration center, which is used to solve the problems of complex configuration and difficult project access operation in the prior art.
In order to achieve the purpose, the invention provides a building method of an Apollo configuration center, which comprises the following steps: creating a ConfigDB database and a PortalDB database and finishing initialization; downloading and installing a Configservice service, an adminService service and a Portal service; and respectively deploying Configservice service, Adminservice and Portal service.
Optionally, Apollo prepares SQL files for the creation of the database, the table and the sample data, respectively, and imports the SQL files into the ConfigDB database and the PortalDB database; the ConfigDB database stores the configuration information of the project in a certain environment; the PortalDB database stores the metadata information of user authority, project and configuration; the Configservice and the Adminservice service share a ConfigDB database; the Portal DB database serves Portal services.
Optionally, the Protal service deploys one service and manages a plurality of environments; the ConfigService service, AdminService and PortalDB database deploy one copy in each environment.
Optionally, the ConfigService service, the AdminService, and the Portal service are sequentially started in sequence.
Optionally, the ConfigService service is an independent micro service, and serves the client to provide configured reading and pushing functions to the client.
Optionally, the client and the ConfigService service maintain long connection, and the configuration update is not lost while the configuration is updated in real time through a pull-and-drag combination mode.
Optionally, the AdminService service is an independent microservice, and serves a Portal service; the Portal service carries out configuration management and release by calling Adminservice; when the Portal service is configured, the environment can be added on the basis of the default environment.
Optionally, the AdminService provides a configuration modification and release function.
Optionally, the Apollo configuration is integrated with the SpringBoot, including the following steps: introducing an Apollo dependent packet; adding an Apollo configuration file; adding an incidence relation between the springBoot application and the Apollo; and ensuring that the SpringBoot obtains Apollo configuration in real time.
Optionally, the configuration file is in a key value form, the configuration file needs to be submitted and issued after being modified, and the configuration file can select an environment to be issued.
Optionally, when the project is restarted, the port configured by Apollo is started.
Compared with the prior art, the technical scheme of the invention has the following advantages: creating a ConfigDB database and a PortalDB database and finishing initialization; downloading and installing a Configservice service, an adminService service and a Portal service; and respectively deploying Configservice service, Adminservice and Portal service. The method can be obtained in real time after the configuration is modified, and projects do not need to be restarted; the invention can also uniformly maintain the configuration files of all projects.
Drawings
FIG. 1 is a block diagram of the Apollo configuration center of the present invention;
Detailed Description
Preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings, but the present invention is not limited to only these embodiments. The invention is intended to cover alternatives, modifications, equivalents and alternatives which may be included within the spirit and scope of the invention.
In the following description of the preferred embodiments of the present invention, specific details are set forth in order to provide a thorough understanding of the present invention, and it will be apparent to those skilled in the art that the present invention may be practiced without these specific details.
The invention is described in more detail in the following paragraphs by way of example with reference to the accompanying drawings. It should be noted that the drawings are in simplified form and are not to precise scale, which is only used for convenience and clarity to assist in describing the embodiments of the present invention.
As shown in fig. 1, a block diagram of the Apollo configuration center of the present invention is illustrated, a ConfigDB database and a PortalDB database are created, and initialization is completed; downloading and installing a Configservice service, an adminService service and a Portal service; and respectively deploying Configservice service, Adminservice and Portal service. The ConfigService service, the adminService service and the Portal service are sequentially started in sequence.
Apollo respectively prepares SQL files for the creation of a database and a table and sample data, and imports the SQL files into a ConfigDB database and a Portal DB database; the ConfigDB database stores the configuration information of the project in a certain environment; the Portal DB database stores metadata information of user rights, items and configurations. The Configservice and the Adminservice service share a ConfigDB database; the Portal DB database serves Portal services.
The ConfigService service is an independent micro service, serves the client and provides configured reading and pushing functions for the client. The client and the ConfigService service keep long connection, and configuration updating is guaranteed not to be lost while configuration real-time updating is achieved through a dragging and pulling combined mode. The AdminService service is an independent micro service and serves a Portal service; the Portal service carries out configuration management and release by calling Adminservice; when the Portal service is configured, the environment can be added on the basis of the default environment. The AdminService service is an independent micro service and serves a Portal service; the Portal service carries out configuration management and release by calling Adminservice; when the Portal service is configured, the environment can be added on the basis of the default environment. Protal service deploys one copy and manages a plurality of environments; the ConfigService service, AdminService and PortalDB database deploy one copy in each environment.
Apollo configuration is integrated with SpringBoot, comprising the steps of:
introducing an Apollo dependent packet (complex group: 'com. ctrip. frame. Apollo', name: 'Apollo-client', version: '1.2.0'); adding annotations: obtaining the configuration file from the configuration center through @ enableloconfig; and adding an incidence relation between the application of the springBoot and the Apollo, and ensuring that the springBoot obtains the Apollo configuration in real time.
For Apollo modified configuration, the configuration file is in a key-value form, the configuration file needs to be submitted and issued after being modified, and the configuration file can select the environment to be issued.
Project local ports may be configured 2000, but project restarts with port starts configured with apollo.
Although the embodiments have been described and illustrated separately, it will be apparent to those skilled in the art that some common techniques may be substituted and integrated between the embodiments, and reference may be made to one of the embodiments not explicitly described, or to another embodiment described.
The above-described embodiments do not limit the scope of the present invention. Any modification, equivalent replacement, and improvement made within the spirit and principle of the above-described embodiments should be included in the protection scope of the technical solution.
Claims (11)
- The building method of the Apollo configuration center is characterized by comprising the following steps of: creating a ConfigDB database and a PortalDB database and finishing initialization; downloading and installing a Configservice service, an adminService service and a Portal service; and respectively deploying Configservice service, Adminservice and Portal service.
- 2. The building method of the Apollo configuration center according to claim 1, characterized in that: apollo respectively prepares SQL files for the creation of a database and a table and sample data, and imports the SQL files into a ConfigDB database and a Portal DB database; the ConfigDB database stores the configuration information of the project in a certain environment; the PortalDB database stores the metadata information of user authority, project and configuration; the Configservice and the Adminservice service share a ConfigDB database; the Portal DB database serves Portal services.
- 3. The building method of the Apollo configuration center according to claim 2, characterized in that: protal service deploys one copy and manages a plurality of environments; the ConfigService service, AdminService and PortalDB database deploy one copy in each environment.
- 4. The building method of the Apollo configuration center according to claim 3, characterized in that: the ConfigService service, the adminService service and the Portal service are sequentially started in sequence.
- 5. The building method of the Apollo configuration center according to claim 4, characterized in that: the ConfigService service is an independent micro service, serves the client and provides configured reading and pushing functions for the client.
- 6. The building method of the Apollo configuration center according to claim 5, characterized in that: the client and the ConfigService service keep long connection, and configuration updating is guaranteed not to be lost while configuration real-time updating is achieved through a dragging and pulling combined mode.
- 7. The building method of the Apollo configuration center according to claim 6, characterized in that: the AdminService service is an independent micro service and serves a Portal service; the Portal service carries out configuration management and release by calling Adminservice; when the Portal service is configured, the environment can be added on the basis of the default environment.
- 8. The building method of the Apollo configuration center according to claim 7, characterized in that: the AdminService provides the functions of modifying and releasing the configuration.
- 9. The method for building an Apollo configuration center according to any one of claims 1 to 8, characterized in that: apollo configuration is integrated with SpringBoot, comprising the steps of: introducing an Apollo dependent packet; adding an Apollo configuration file; adding an incidence relation between the springBoot application and the Apollo; and ensuring that the SpringBoot obtains Apollo configuration in real time.
- 10. The method for building an Apollo configuration center according to any one of claims 1 to 8, characterized in that: the Apollo configuration file is in a key value form, needs to be submitted and issued after being modified, and can select an environment to be issued.
- 11. The method for building an Apollo configuration center according to any one of claims 1 to 8, characterized in that: when the project is restarted, the port configured with Apollo starts.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911378664.0A CN111131472A (en) | 2019-12-27 | 2019-12-27 | Building method of Apollo configuration center |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911378664.0A CN111131472A (en) | 2019-12-27 | 2019-12-27 | Building method of Apollo configuration center |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111131472A true CN111131472A (en) | 2020-05-08 |
Family
ID=70504207
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911378664.0A Pending CN111131472A (en) | 2019-12-27 | 2019-12-27 | Building method of Apollo configuration center |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111131472A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112187662A (en) * | 2020-09-16 | 2021-01-05 | 银盛支付服务股份有限公司 | Apollo-based traffic distribution method |
| CN112328322A (en) * | 2020-10-26 | 2021-02-05 | 银盛支付服务股份有限公司 | Apollo configuration localization method and system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090276447A1 (en) * | 2008-05-05 | 2009-11-05 | Microsoft Corporation | Formats for database template files shared between client and server environments |
| CN108540529A (en) * | 2018-03-07 | 2018-09-14 | 江苏电力信息技术有限公司 | Do not restart dynamic parameter method for refreshing under a kind of framework based on micro services |
| CN109995586A (en) * | 2019-03-25 | 2019-07-09 | 江苏电力信息技术有限公司 | Refresh model with dynamic configuration parameters based on the unified configuration under micro services framework |
-
2019
- 2019-12-27 CN CN201911378664.0A patent/CN111131472A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090276447A1 (en) * | 2008-05-05 | 2009-11-05 | Microsoft Corporation | Formats for database template files shared between client and server environments |
| CN108540529A (en) * | 2018-03-07 | 2018-09-14 | 江苏电力信息技术有限公司 | Do not restart dynamic parameter method for refreshing under a kind of framework based on micro services |
| CN109995586A (en) * | 2019-03-25 | 2019-07-09 | 江苏电力信息技术有限公司 | Refresh model with dynamic configuration parameters based on the unified configuration under micro services framework |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112187662A (en) * | 2020-09-16 | 2021-01-05 | 银盛支付服务股份有限公司 | Apollo-based traffic distribution method |
| CN112328322A (en) * | 2020-10-26 | 2021-02-05 | 银盛支付服务股份有限公司 | Apollo configuration localization method and system |
| CN112328322B (en) * | 2020-10-26 | 2023-08-01 | 银盛支付服务股份有限公司 | Method and system for localization of Apollo configuration |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7167874B2 (en) | System and method for command line administration of project spaces using XML objects | |
| US7590669B2 (en) | Managing client configuration data | |
| US11509646B2 (en) | Systems and methods for cloning an agent in a distributed environment | |
| US8615501B2 (en) | Hypervisor service to provide image version control support | |
| US9772911B2 (en) | Pooling work across multiple transactions for reducing contention in operational analytics systems | |
| US20070143379A1 (en) | Metadata driven deployment of applications | |
| US10216510B2 (en) | Silent upgrade of software with dependencies | |
| US20020174422A1 (en) | Software distribution system | |
| US10372555B1 (en) | Reversion operations for data store components | |
| CN113168345A (en) | Streamlined secure deployment of cloud services | |
| US20180343300A1 (en) | Methods and apparatus to perform data migration in a distributed environment | |
| US8082406B1 (en) | Techniques for reducing data storage needs using CDP/R | |
| US10338910B2 (en) | Multi-tenant upgrading | |
| CN110098952A (en) | A kind of management method and device of server | |
| KR20220083838A (en) | Method and apparatus for creating a mirror image file, and a computer-readable storage medium | |
| CN111131472A (en) | Building method of Apollo configuration center | |
| US10783073B2 (en) | Chronologically ordered out-of-place update key-value storage system | |
| CN109684028A (en) | A kind of method, device and equipment that operating system is separated with user data | |
| JPH08137768A (en) | Remote distribution management network system | |
| US20090254579A1 (en) | Deploying directory instances | |
| JP5943753B2 (en) | Virtual machine management system, virtual machine management method and program | |
| AU2021268828B2 (en) | Secure data replication in distributed data storage environments | |
| US10162626B2 (en) | Ordered cache tiering for program build files | |
| Shao | About the design changes required for enabling ECM systems to exploit cloud technology | |
| US11593498B2 (en) | Distribution of user specific data elements in a replication environment |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200508 |
|
| RJ01 | Rejection of invention patent application after publication |