CN112667348B - MySQL containerization method and system and computer equipment - Google Patents
MySQL containerization method and system and computer equipment Download PDFInfo
- Publication number
- CN112667348B CN112667348B CN202011509765.XA CN202011509765A CN112667348B CN 112667348 B CN112667348 B CN 112667348B CN 202011509765 A CN202011509765 A CN 202011509765A CN 112667348 B CN112667348 B CN 112667348B
- Authority
- CN
- China
- Prior art keywords
- database
- capacity
- mysql
- strategy
- containerization
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 40
- 238000012545 processing Methods 0.000 claims description 27
- 238000011002 quantification Methods 0.000 claims description 19
- 238000004590 computer program Methods 0.000 claims description 5
- 238000004364 calculation method Methods 0.000 claims description 3
- 238000003860 storage Methods 0.000 claims description 3
- 238000010276 construction Methods 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 6
- 238000013508 migration Methods 0.000 description 3
- 230000005012 migration Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 238000007418 data mining Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to a MySQL containerization method, a MySQL containerization system and computer equipment, wherein the MySQL containerization method comprises the following steps: acquiring target data characteristics in database requirements to obtain a target database type; acquiring a target database capacity deployment strategy; according to a target database capacity deployment strategy and a capacity corresponding strategy virtual database hardware system, obtaining MySQL capacity quantified capacity virtual hardware; configuring preset standard service business to each corresponding capacity virtual hardware and capacity database capacity according to the business correspondence to form a MySQL containerized database framework; and receiving a service request, analyzing to obtain service characteristics, corresponding the service characteristics to the capacity of each capacity database, and operating in a MySQL containerized database framework. The invention provides a MySQL containerization scheme which is high in performance, stable and easy to expand and migrate.
Description
Technical Field
The invention relates to the technical field of data processing, in particular to a MySQL containerization method, a MySQL containerization device and computer equipment.
Background
With the rapid development of computer network technology in recent years, internet enterprises provide more and more applications and personalized services for users, and with the increase of massive data submitted by users, the enterprises must process the data timely and correctly and feed back results to the users. Information analysis and data mining techniques for large-scale data are becoming hot spots. The need for programming models and computational efficiency for large-scale data processing has been one of the biggest hotspots in the research field.
At present, traditional banks and financial institutions do not basically realize containerization database service, with the rapid development of container technology in China, container clouds are gradually known by developers, but the container clouds have certain gaps in practical application compared with traditional cloud hosts. In the traditional financial industry, production business is really run on a container cloud platform, and the production business is not existed at present, the main reasons are that the containerization of the DB is not mature enough, no mature solution is available, the DB migration cost is too high, and the migration time period is too long.
Based on the above problems, how to provide a high-performance, stable, easy-to-expand and easy-to-migrate solution is a technical problem to be solved in the art.
Disclosure of Invention
The invention aims to provide a MySQL containerization method, a MySQL containerization device and computer equipment aiming at the defects of the prior art. The object of the present invention can be achieved by the following technical means.
The invention provides a MySQL containerization method, which comprises the following steps:
presetting a deployment strategy corresponding relation between a database type and a database capacity deployment strategy in a MySQL database; setting a capacity corresponding strategy between the middleware of the MySQL database and the capacity of the database, and setting a business corresponding relation between the capacity of the database and a standard service business;
acquiring target data characteristics in database requirements, and acquiring a target database type according to a preset data characteristic and database type corresponding relation; acquiring a target database capacity deployment strategy according to the target database type and the deployment strategy corresponding relation;
acquiring a database hardware system of the MySQL database based on the middleware of the MySQL database, and virtualizing the database hardware system according to the target database capacity deployment strategy and the capacity corresponding strategy to obtain capacity virtual hardware with MySQL capacity quantification; configuring preset standard service business to each corresponding capacity quantification virtual hardware and capacity quantification database capacity according to the business corresponding relation to form a MySQL containerized database framework;
and receiving a service request, analyzing to obtain service characteristics, corresponding the service characteristics to the capacity of each capacity database, and operating in the MySQL containerized database framework.
Optionally, the setting of the capacity correspondence policy between the middleware of the MySQL database and the capacity of the database includes:
setting the number and identification marks of the middleware of the MySQL database, and capacity content and capacity marks of the database capacity;
and setting a capacity corresponding strategy according to the middleware quantity and the identification mark, the capacity content of the database capacity and the capacity mark and according to the one-to-one strategy between the middleware and the database capacity.
Optionally, wherein the method further comprises:
obtaining a target distributed deployment strategy according to the middleware and database capacity of the MySQL database and the type of the target database and the corresponding relation of a preset distributed deployment strategy;
building a distributed MySQL containerization processing framework according to the target distributed deployment strategy and the capacity of each middleware and database;
and configuring preset standard service business to the capacity quantification virtual hardware and capacity quantification database capacity corresponding to each distributed MySQL containerized processing framework according to the business correspondence to form a MySQL containerized database framework.
Optionally, wherein the method further comprises:
acquiring a corresponding target resource scheduling strategy according to the target distributed deployment strategy, and establishing a distributed task message queue according to the target resource scheduling strategy; correspondingly connecting each task management element in the distributed task message queue with each distributed data layer of the distributed MySQL containerization processing framework according to the corresponding relation between the distributed deployment strategy and the resource scheduling strategy;
and calling the distributed data in the distributed MySQL containerization processing framework to perform data calculation processing based on the target resource scheduling strategy.
Optionally, wherein the method further comprises:
presetting a corresponding relation between a database type and a right management strategy of an access client;
when an access client is detected, acquiring the authority of the access client according to the corresponding relation of the authority management strategy; and calling a corresponding resource scheduling strategy according to the authority of the access client.
Optionally, wherein the method further comprises:
in the distributed MySQL containerization processing framework, a central server, terminal equipment and a virtual server which is created within a preset range according to a preset strategy are arranged;
the terminal equipment is connected with the virtual servers, the virtual servers are connected with the central server, a plurality of terminal servers correspond to one virtual server, and a plurality of virtual servers correspond to one central server;
and storing the target distributed deployment strategy, the target resource scheduling strategy and the scheduled target data into the corresponding virtual server according to a preset storage strategy.
In another aspect, the present invention further provides a MySQL containerization system, including: the system comprises a MySQL containerization setting module, a MySQL containerization strategy deployment module, a MySQL containerization building module and a MySQL containerization operation module; wherein,
the MySQL containerization setting module is used for presetting a corresponding relation between a database type in a MySQL database and a deployment strategy of a database capacity deployment strategy; setting a capacity corresponding strategy between the middleware of the MySQL database and the capacity of the database, and setting a business corresponding relation between the capacity of the database and a standard service business;
the MySQL containerization strategy deployment module is connected with the MySQL containerization setting module, acquires target data characteristics in database requirements, and obtains a target database type according to a preset data characteristic and database type corresponding relation; acquiring a target database capacity deployment strategy according to the target database type and the deployment strategy corresponding relation;
the MySQL containerization building module is connected with the MySQL containerization strategy deployment module, acquires a database hardware system of the MySQL database based on a middleware of the MySQL database, and virtualizes the database hardware system according to the target database capacity deployment strategy and the capacity corresponding strategy to obtain MySQL capacity quantified volumetric virtual hardware; configuring preset standard service business to each corresponding capacity quantification virtual hardware and capacity quantification database capacity according to the business corresponding relation to form a MySQL containerized database framework;
the MySQL containerized operation module is connected with the MySQL containerized building module, receives a service request, analyzes the service request to obtain service characteristics, corresponds the service characteristics to the capacity of each capacity database, and operates in the MySQL containerized database framework.
Optionally, the MySQL containerization setting module includes: the MySQL containerized deployment strategy setting unit and the database capacity setting unit;
the MySQL containerized deployment strategy setting unit is used for presetting a deployment strategy corresponding relation between a database type and a database capacity deployment strategy in a MySQL database; setting a capacity corresponding strategy between the middleware of the MySQL database and the capacity of the database, and setting a business corresponding relation between the capacity of the database and a standard service business;
the database capacity setting unit is connected with the MySQL containerized deployment strategy setting unit and is used for setting the number and the identification identifier of the middleware of the MySQL database and the capacity content and the capacity identifier of the database capacity;
and setting a capacity corresponding strategy according to the middleware quantity and the identification mark, the capacity content of the database capacity and the capacity mark and according to the one-to-one strategy between the middleware and the database capacity.
Optionally, wherein the system further comprises: the distributed deployment module is connected with the MySQL containerized building module and is used for:
obtaining a target distributed deployment strategy according to the middleware and database capacity of the MySQL database and the type of the target database and the corresponding relation of a preset distributed deployment strategy;
building a distributed MySQL containerization processing framework according to the target distributed deployment strategy and the capacity of each middleware and database;
and configuring preset standard service business to the capacity quantification virtual hardware and capacity quantification database capacity corresponding to each distributed MySQL containerized processing framework according to the business correspondence to form a MySQL containerized database framework.
In another aspect, the present invention also provides a computer device comprising a memory in which is stored a computer program and a processor which, when executing the computer program, implements the steps of the MySQL containerization method of any of claims 1 to 6.
Compared with the prior art, the invention has the beneficial effects that:
according to the MySQL containerization method, the MySQL containerization system and the computer equipment, the container is established faster than the virtual machine, and the light-weight script of the container can reduce the overhead in the aspects of performance and size. Containers improve developer productivity by removing cross-service dependencies and conflicts. Each container can be used as a different micro-service and can be upgraded independently without worrying about synchronization. The container has no extra overhead of a management program, has better performance and lower system load with a bottom shared operating system, can run more application examples under the same condition, and can more fully utilize system resources. Meanwhile, the container has good resource isolation and limiting capacity, resources such as a CPU (Central processing Unit) and a memory can be accurately and correspondingly distributed, and mutual influence among applications is avoided. Environment standardization and version control, with version control for each container's mirror, allows tracking of different versions of containers, monitoring for differences between versions, and the like. Based on the environment consistency and standardization provided by the container, tools such as Gt and the like can be used for carrying out version control on the container mirror image, compared with the code-based version control, the version control can be realized on the whole application running environment, and the rollback can be quickly carried out once a fault occurs. Compared with the prior virtual machine mirror image, the container compression and backup speed is higher, and the mirror image starting is as fast as starting a common process. The runtime environment is portable, and the container encapsulates all the relevant details necessary to run the application, so that the migration of images from one environment to another is more flexible. Can be standardized, most containers are based on open standards, and can be operated on all mainstream Linux distribution, Microsoft platforms, and the like. The processes between containers are isolated from each other, as is the infrastructure therein, so that an upgrade or change to one of the containers does not affect the other containers.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a schematic flow chart of a MySQL containerization method in an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a second MySQL containerization method according to an embodiment of the present invention;
FIG. 3 is a flowchart illustrating a third MySQL containerization method according to an embodiment of the present invention;
FIG. 4 is a flowchart illustrating a fourth MySQL containerization method according to an embodiment of the present invention;
FIG. 5 is a flowchart illustrating a fifth MySQL containerization method according to an embodiment of the present invention;
FIG. 6 is a flowchart illustrating a sixth MySQL containerization method according to an embodiment of the present invention;
FIG. 7 is a schematic structural diagram of a MySQL containerization system in an embodiment of the invention;
FIG. 8 is a structural diagram of a second MySQL containerization system according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of a third MySQL containerization system according to an embodiment of the present invention.
Detailed Description
The technical solutions of the present invention will be described clearly and completely with reference to specific embodiments, and it should be understood that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 is a schematic flow chart of a MySQL containerization method in this embodiment. Specifically, the method comprises the following steps:
102, acquiring target data characteristics in database requirements, and obtaining a target database type according to a preset data characteristic and database type corresponding relation; and acquiring a target database capacity deployment strategy according to the type of the target database and the corresponding relation of the deployment strategy.
103, acquiring a database hardware system of the MySQL database based on the middleware of the MySQL database, and deploying a strategy and a capacity corresponding strategy virtual database hardware system according to the capacity of the target database to obtain capacity virtual hardware with MySQL capacity quantification; and configuring the preset standard service business to each corresponding capacity virtual hardware and capacity database capacity according to the business correspondence to form a MySQL containerized database framework.
And step 104, receiving the service request, analyzing to obtain service characteristics, corresponding the service characteristics to the capacity of each capacity database, and operating in the MySQL containerized database framework.
In some optional embodiments, as shown in fig. 2, a schematic flow chart of a second MySQL containerization method in this implementation is different from that in fig. 1, further including:
In some optional embodiments, as shown in fig. 3, which is a schematic flow chart of a third MySQL containerization method in this implementation, different from that in fig. 1, the method further includes:
And 302, building a distributed MySQL containerization processing framework according to the target distributed deployment strategy and the capacity of each middleware and database.
And 303, configuring preset standard service business to each corresponding capacity virtual hardware and capacity database capacity in the distributed MySQL containerized processing framework according to the business correspondence to form a MySQL containerized database framework.
In some optional embodiments, as shown in fig. 4, which is a schematic flow chart of a fourth MySQL containerization method in this implementation, different from fig. 3, the method further includes:
And step 402, calling distributed data in the distributed MySQL containerization processing framework to perform data calculation processing based on the target resource scheduling strategy.
In some optional embodiments, as shown in fig. 5, a schematic flow chart of a fifth MySQL containerization method in this implementation is different from that in fig. 4, further including:
In some optional embodiments, as shown in fig. 6, a schematic flow chart of a sixth MySQL containerization method in this implementation is different from that in fig. 4, further including:
In some optional embodiments, as shown in fig. 7, which is a schematic diagram of the MySQL containerization system in this embodiment, the apparatus is used to implement the MySQL containerization method described above. Specifically, the system comprises: the system comprises a MySQL containerization setting module 701, a MySQL containerization strategy deployment module 702, a MySQL containerization construction module 703 and a MySQL containerization operation module 704.
The MySQL containerization setting module 701 presets a deployment strategy corresponding relation between a database type in a MySQL database and a database capacity deployment strategy; setting a capacity corresponding strategy between the middleware of the MySQL database and the capacity of the database, and setting a business corresponding relation between the capacity of the database and the standard service business.
The MySQL containerization strategy deployment module 702 is connected with the MySQL containerization setting module 701, acquires target data characteristics in database requirements, and obtains a target database type according to a preset data characteristic and database type corresponding relation; and acquiring a target database capacity deployment strategy according to the type of the target database and the corresponding relation of the deployment strategy.
The MySQL containerization building module 703 is connected with the MySQL containerization strategy deployment module 702, acquires a database hardware system of the MySQL database based on a middleware of the MySQL database, and deploys a strategy and a strategy virtual database hardware system corresponding to the capacity according to the capacity of a target database to obtain MySQL capacity quantified volumetric virtual hardware; and configuring the preset standard service business to each corresponding capacity virtual hardware and capacity database capacity according to the business correspondence to form a MySQL containerized database framework.
The MySQL containerized operation module 704 is connected with the MySQL containerized building module 703, receives the service request, analyzes the service request to obtain service characteristics, corresponds the service characteristics to each capacity of the capacity database, and operates in the MySQL containerized database framework.
In some optional embodiments, as shown in fig. 8, which is a schematic diagram of a second MySQL containerization system in this implementation, unlike in fig. 7, the MySQL containerization setting module 701 includes: a MySQL containerized deployment policy setting unit 711 and a database capacity setting unit 712.
The MySQL containerized deployment policy setting unit 711 presets a deployment policy corresponding relationship between a database type in a MySQL database and a database capacity deployment policy; setting a capacity corresponding strategy between the middleware of the MySQL database and the capacity of the database, and setting a business corresponding relation between the capacity of the database and the standard service business.
The database capacity setting unit 712 is connected with the MySQL containerized deployment policy setting unit 711 and is used for setting the number and the identification identifier of the middleware of the MySQL database and the capacity content and the capacity identifier of the database capacity; and setting a capacity corresponding strategy according to the one-to-one strategy between the middleware and the database capacity according to the number and the identification mark of the middleware, the capacity content of the database capacity and the capacity mark.
In some optional embodiments, as shown in fig. 9, a schematic diagram of a third MySQL containerization system in this implementation is different from that in fig. 7, further including: the distributed deployment module 901 is connected to the MySQL containerization building module 703, and is configured to:
and obtaining a target distributed deployment strategy according to the middleware of the MySQL database, the database capacity and the target database type and the corresponding relation of the preset distributed deployment strategy.
And building a distributed MySQL containerization processing framework according to the target distributed deployment strategy and the capacity of each middleware and database.
And configuring the preset standard service business to the capacity virtual hardware and the capacity database corresponding to each distributed MySQL containerized processing frame according to the business correspondence to form a MySQL containerized database framework.
In some alternative embodiments, there is provided a computer device comprising a memory and a processor, the memory having stored therein a computer program, the processor when executing the computer program implementing the steps of the MySQL containerization method as above.
The present invention has been further described with reference to specific embodiments, but it should be understood that the detailed description should not be construed as limiting the spirit and scope of the present invention, and various modifications made to the above-described embodiments by those of ordinary skill in the art after reading this specification are within the scope of the present invention.
Claims (8)
1. A MySQL containerization method is characterized by comprising the following steps:
presetting a deployment strategy corresponding relation between a database type and a database capacity deployment strategy in a MySQL database; setting a capacity corresponding strategy between the middleware of the MySQL database and the capacity of the database, and setting a business corresponding relation between the capacity of the database and a standard service business;
acquiring target data characteristics in database requirements, and acquiring a target database type according to a preset data characteristic and database type corresponding relation; acquiring a target database capacity deployment strategy according to the target database type and the deployment strategy corresponding relation;
acquiring a database hardware system of the MySQL database based on the middleware of the MySQL database, and virtualizing the database hardware system according to the target database capacity deployment strategy and the capacity corresponding strategy to obtain capacity virtual hardware with MySQL capacity quantification; configuring preset standard service business to each corresponding capacity quantification virtual hardware and capacity quantification database capacity according to the business corresponding relation to form a MySQL containerized database framework;
receiving a service request, analyzing the service request to obtain service characteristics, corresponding the service characteristics to the capacity of each capacity database, and operating in the MySQL containerized database framework;
obtaining a target distributed deployment strategy according to the middleware and database capacity of the MySQL database and the type of the target database and the corresponding relation of a preset distributed deployment strategy;
building a distributed MySQL containerization processing framework according to the target distributed deployment strategy and the capacity of each middleware and database;
and configuring preset standard service business to the capacity quantification virtual hardware and capacity quantification database capacity corresponding to each distributed MySQL containerized processing framework according to the business correspondence to form a MySQL containerized database framework.
2. The MySQL containerization method of claim 1, wherein setting a capacity correspondence policy between middleware of the MySQL database and database capacity is:
setting the number and identification marks of the middleware of the MySQL database, and capacity content and capacity marks of the database capacity;
and setting a capacity corresponding strategy according to the middleware quantity and the identification mark, the capacity content of the database capacity and the capacity mark and according to the one-to-one strategy between the middleware and the database capacity.
3. The MySQL containerization method of claim 1, further comprising:
acquiring a corresponding target resource scheduling strategy according to the target distributed deployment strategy, and establishing a distributed task message queue according to the target resource scheduling strategy; correspondingly connecting each task management element in the distributed task message queue with each distributed data layer of the distributed MySQL containerization processing framework according to the corresponding relation between the distributed deployment strategy and the resource scheduling strategy;
and calling the distributed data in the distributed MySQL containerization processing framework to perform data calculation processing based on the target resource scheduling strategy.
4. The MySQL containerization method of claim 3, further comprising:
presetting a corresponding relation between a database type and a right management strategy of an access client;
when an access client is detected, acquiring the authority of the access client according to the corresponding relation of the authority management strategy; and calling a corresponding resource scheduling strategy according to the authority of the access client.
5. The MySQL containerization method of claim 3, further comprising:
in the distributed MySQL containerization processing framework, a central server, terminal equipment and a virtual server which is created within a preset range according to a preset strategy are arranged;
the terminal equipment is connected with the virtual servers, the virtual servers are connected with the central server, a plurality of terminal servers correspond to one virtual server, and a plurality of virtual servers correspond to one central server;
and storing the target distributed deployment strategy, the target resource scheduling strategy and the scheduled target data into the corresponding virtual server according to a preset storage strategy.
6. A MySQL containerization system comprising: the system comprises a MySQL containerization setting module, a MySQL containerization strategy deployment module, a MySQL containerization building module, a MySQL containerization operation module and a distributed deployment module; wherein,
the MySQL containerization setting module is used for presetting a corresponding relation between a database type in a MySQL database and a deployment strategy of a database capacity deployment strategy; setting a capacity corresponding strategy between the middleware of the MySQL database and the capacity of the database, and setting a business corresponding relation between the capacity of the database and a standard service business;
the MySQL containerization strategy deployment module is connected with the MySQL containerization setting module, acquires target data characteristics in database requirements, and obtains a target database type according to a preset data characteristic and database type corresponding relation; acquiring a target database capacity deployment strategy according to the target database type and the deployment strategy corresponding relation;
the MySQL containerization building module is connected with the MySQL containerization strategy deployment module, acquires a database hardware system of the MySQL database based on a middleware of the MySQL database, and virtualizes the database hardware system according to the target database capacity deployment strategy and the capacity corresponding strategy to obtain MySQL capacity quantified volumetric virtual hardware; configuring preset standard service business to each corresponding capacity quantification virtual hardware and capacity quantification database capacity according to the business corresponding relation to form a MySQL containerized database framework;
the MySQL containerized operation module is connected with the MySQL containerized building module, receives a service request, analyzes the service request to obtain service characteristics, corresponds the service characteristics to the capacity of each capacity database, and operates in the MySQL containerized database framework;
the distributed deployment module is connected with the MySQL containerized construction module and is used for:
obtaining a target distributed deployment strategy according to the middleware and database capacity of the MySQL database and the type of the target database and the corresponding relation of a preset distributed deployment strategy;
building a distributed MySQL containerization processing framework according to the target distributed deployment strategy and the capacity of each middleware and database;
and configuring preset standard service business to the capacity quantification virtual hardware and capacity quantification database capacity corresponding to each distributed MySQL containerized processing framework according to the business correspondence to form a MySQL containerized database framework.
7. The MySQL containerization system of claim 6, wherein the MySQL containerization setup module comprises: the MySQL containerized deployment strategy setting unit and the database capacity setting unit;
the MySQL containerized deployment strategy setting unit is used for presetting a deployment strategy corresponding relation between a database type and a database capacity deployment strategy in a MySQL database; setting a capacity corresponding strategy between the middleware of the MySQL database and the capacity of the database, and setting a business corresponding relation between the capacity of the database and a standard service business;
the database capacity setting unit is connected with the MySQL containerized deployment strategy setting unit and is used for setting the number and the identification identifier of the middleware of the MySQL database and the capacity content and the capacity identifier of the database capacity;
and setting a capacity corresponding strategy according to the middleware quantity and the identification mark, the capacity content of the database capacity and the capacity mark and according to the one-to-one strategy between the middleware and the database capacity.
8. A computer device comprising a memory having stored therein a computer program and a processor which when executed implements the steps of the MySQL containerization method of any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011509765.XA CN112667348B (en) | 2020-12-19 | 2020-12-19 | MySQL containerization method and system and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011509765.XA CN112667348B (en) | 2020-12-19 | 2020-12-19 | MySQL containerization method and system and computer equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112667348A CN112667348A (en) | 2021-04-16 |
| CN112667348B true CN112667348B (en) | 2021-10-29 |
Family
ID=75407276
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011509765.XA Active CN112667348B (en) | 2020-12-19 | 2020-12-19 | MySQL containerization method and system and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112667348B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110806907A (en) * | 2019-10-31 | 2020-02-18 | 浪潮云信息技术有限公司 | Containerized configurable database execution script management system and method |
| WO2020091591A1 (en) * | 2018-10-30 | 2020-05-07 | Mimos Berhad | A system and method for enabling vulnerability detection of cloud container based service deployment |
| CN111211930A (en) * | 2019-12-31 | 2020-05-29 | 杭州趣链科技有限公司 | Block chain service disaster-tolerant backup containerized deployment method |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104715787A (en) * | 2013-12-14 | 2015-06-17 | 上海莞东拿信息科技有限公司 | Novel passive matrix addressing data storage device with power-off protection |
| CN106445675B (en) * | 2016-10-20 | 2019-12-31 | 焦点科技股份有限公司 | B2B platform distributed application scheduling and resource allocation method |
| US10470059B1 (en) * | 2019-03-04 | 2019-11-05 | Cisco Technology, Inc. | Dynamic network device selection for containerized application deployment |
| CN111752675B (en) * | 2020-05-27 | 2024-03-15 | 南京认知物联网研究院有限公司 | Internet of things platform based on containerization technology |
-
2020
- 2020-12-19 CN CN202011509765.XA patent/CN112667348B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020091591A1 (en) * | 2018-10-30 | 2020-05-07 | Mimos Berhad | A system and method for enabling vulnerability detection of cloud container based service deployment |
| CN110806907A (en) * | 2019-10-31 | 2020-02-18 | 浪潮云信息技术有限公司 | Containerized configurable database execution script management system and method |
| CN111211930A (en) * | 2019-12-31 | 2020-05-29 | 杭州趣链科技有限公司 | Block chain service disaster-tolerant backup containerized deployment method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112667348A (en) | 2021-04-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110417613B (en) | Distributed performance testing method, device, equipment and storage medium based on Jmeter | |
| CN112667362B (en) | Method and system for deploying Kubernetes virtual machine cluster on Kubernetes | |
| CN111212116A (en) | High-performance computing cluster creating method and system based on container cloud | |
| US10728169B1 (en) | Instance upgrade migration | |
| US9959157B1 (en) | Computing instance migration | |
| CN103077034B (en) | hybrid virtualization platform JAVA application migration method and system | |
| CN111752581B (en) | Upgrading method and device of distributed system and computer system | |
| CN103873534A (en) | Method and device for application cluster migration | |
| CN116601606A (en) | Multi-tenant control plane management on a computing platform | |
| CN112433812B (en) | Virtual machine cross-cluster migration method, system, equipment and computer medium | |
| CN111669284A (en) | OpenStack automatic deployment method, electronic device, storage medium and system | |
| US20230004414A1 (en) | Automated instantiation and management of mobile networks | |
| CN109032757B (en) | System framework automatic deployment time optimization method based on cloud platform | |
| CN116800616B (en) | Management method and related device of virtualized network equipment | |
| CN110502392A (en) | Cloud platform management and monitoring system | |
| US20240143377A1 (en) | Overlay container storage driver for microservice workloads | |
| CN113162802A (en) | Communication method, equipment and storage medium based on InfiniBand | |
| CN115943365A (en) | Method and system for instantiating and transparently migrating a containerized process in execution | |
| CN110704851A (en) | Public cloud data processing method and device | |
| US11561843B2 (en) | Automated performance tuning using workload profiling in a distributed computing environment | |
| CA3183412A1 (en) | Methods and systems for managing computing virtual machine instances | |
| JP2024501005A (en) | Management method and device for container clusters | |
| CN112667348B (en) | MySQL containerization method and system and computer equipment | |
| CN116225617A (en) | Management migration method and device for container instance, electronic equipment and storage medium | |
| CN113326098B (en) | Cloud management platform supporting KVM virtualization and container virtualization |
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 | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 518000 Room 201, building A, No. 1, Qian Wan Road, Qianhai Shenzhen Hong Kong cooperation zone, Shenzhen, Guangdong (Shenzhen Qianhai business secretary Co., Ltd.) Applicant after: Feisuanzhi Technology (Shenzhen) Co.,Ltd. Address before: 208e-10, port building, shipping center, 59 Linhai Avenue, Nanshan street, Qianhai Shenzhen Hong Kong cooperation zone, Shenzhen, Guangdong 518000 Applicant before: Qianhai feisuan Technology (Shenzhen) Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |