Shulou(Shulou.com)05/31 Report--

This article mainly introduces "how to plan database environment standardization management". In daily operation, I believe many people have doubts about how to plan database environment standardization management. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful for you to answer the doubts of "how to plan database environment standardization management"! Next, please follow the editor to study!

Generally speaking, when the business can run stably, people mainly focus on the management of the online environment, on the contrary, they do not pay enough attention to the management of other environments, but the reality is that the management of these environments needs to be standardized. Through overall management to reduce some potential hidden dangers, in order to reduce the hidden dangers of the online environment to a certain extent.

Assuming that other environments are driveways and the online environment is controlled by traffic lights, if the road is seriously blocked or even unavailable, it is very dangerous for traffic to run steadily.

The same is true of the standardized management of the database environment, which is easy to ignore but matters a lot.

First of all, we need to be clear about the database products, such as the standard version, cluster version, stand-alone version, so that the management mode for the environment is also different. For example, the standard version needs to consider high availability, while the underlying data sharding node of the cluster version is actually the standard version, which involves distributed cluster management and high availability management in terms of management mode.

Then let's talk about the relevant database environment.

The development environment, usually used by itself on the development side, is mainly designed to be efficient.

The test environment, which corresponds to the test server, will be adapted to a certain proportion according to the type of online environment (stand-alone version and cluster version). The main purpose is to be efficient, and of course, security needs to be taken into account at the same time.

The pre-release environment, which has the same permission configuration as the online environment and has a separate pre-release application server, is a key station for publishing to online verification.

Online environment, the top priority, is to improve efficiency and ensure security on the basis of stable operation, and it is also the lifeblood of the stable operation of the business.

In addition, there are data statistical analysis environment, big data analysis environment and so on, because the area of such expansion will be larger, so I will not repeat it.

With this information, let's take a look at the management blueprint of the underlying environment.

In fact, this is a link that connects data from beginning to end, and the part on the left is worth mentioning, that is, database resource delivery. We can hardly remember which test database resources have been delivered to developers. Generally speaking, most of these work can be done by creating databases for self-help, so the part of resource delivery is important to solve the problem of rapid delivery in online environment. For example, if your backend executes for 1 minute, but it takes 20 minutes for the front end to prepare the environment to complete the requirements submission, then the same delivery efficiency is still in question. The management of the development environment is even more scattered, some development groups buy their own servers to build the environment, and some are mixed with the development environment and the test environment.

And the pre-release environment many developers feel that there is some trouble, resulting in the pre-release environment has become a chicken rib, may also be almost, undesirable and useless.

So what does environmental standardization management mainly do? this needs to lead to the scope of standardized management. In general, we have planned the following parts.

Database version unified planning and upgrade, for example, online environment is 5.7, then the test environment should also be the same version, by the same token, version management between other environments should also be synchronized

Operating system standardized management, operating system, file system and command usage patterns are also different under different operating systems and versions, and need to be able to be unified and refer to stable and newer versions

Backup recovery full coverage, whether in the test environment or online environment, need to consider backup recovery, this is the backup granularity and recovery capabilities are different.

Database topology relationship support, for one master one slave, one master multi-slave environment how to effectively manage the topology, is the core of high-availability management, of course, open source software in the industry also has its own way of implementation. I think it is the most important to be able to grasp the most essential topology management.

Metadata lifecycle management, if there is no lifecycle management of metadata, it will be more embarrassing. For example, after a 10.10.10.10 server is offline, the IP is still 10.10.10.10. If the metadata is poorly managed in multiple dimensions, it will lead to misleading or even misoperation.

Security audit, development business students how to correctly use the online environment, involving the security specifications of the environment, and to a certain extent develop limited access, all processes provide audit support.

On the basis of the above, I summarized the current environmental management problems, but also found many problems, the red part is I specifically marked the need to focus on improvement.

Through the disassembly of the focus of the task, coupled with the time plan, we will deduce some things and feasibility to be done in this direction of work.

Of course, the important point is that the standardized management of the environment is a continuous project, and it is best to achieve a reasonable balance on the whole.

At this point, the study on "how to plan the standardized management of database environment" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.