|
1 | 1 | <p align="center">
|
2 |
| -<img style="padding: 0 15px; float: left;" src="images/logo.png" width="70"> |
| 2 | +<img style="padding: 0 15px; float: left;" src="images/mysql-mariadb-percona-logo.svg" width="70"> |
3 | 3 | </p>
|
4 | 4 |
|
5 |
| -## MariaDB/MySQL Auto-Сlustering with Embedded Load Balancing and Replication Types Selection |
| 5 | +## MySQL/MariaDB/Percona Auto-Сlustering with Embedded Load Balancing and Replication Types Selection |
6 | 6 |
|
7 |
| -MariaDB/MySQL Auto-Clustering solution is packaged as an advanced highly available and auto-scalable cluster on top of managed Jelastic dockerized stack templates. |
| 7 | +MySQL/MariaDB/Percona Auto-Clustering solution is packaged as an advanced highly available and auto-scalable cluster on top of managed dockerized stack templates. |
8 | 8 |
|
9 | 9 | <p align="left">
|
10 |
| -<img src="images/mysql-maria-scheme-new.svg" width="500"> |
| 10 | +<img src="images/mysql-maria-percona-scheme.svg" width="500"> |
11 | 11 | </p>
|
12 | 12 |
|
13 |
| -The package includes Highly Available [*ProxySQL Load Balancer*](http://www.proxysql.com) and [*Cluster Orchestrator*](https://github.com/github/orchestrator) to manage MariaDB/MySQL replication topology. And there is a choice between different MariaDB/MySQL replication types: |
| 13 | +The package includes Highly Available [*ProxySQL Load Balancer*](http://www.proxysql.com) and [*Cluster Orchestrator*](https://github.com/github/orchestrator) to manage MySQL/MariaDB/Percona replication topology. And there is a choice between different MySQL/MariaDB/Percona replication types: |
14 | 14 |
|
15 |
| -## Simple MariaDB/MySQL Replication |
| 15 | +## Simple MySQL/MariaDB/Percona Replication |
16 | 16 |
|
17 | 17 | * *primary*-*secondary*(*source*-*replica*) - provides a good consistency (i.e. exactly one node to modify data), but no automatic failover upon primary failure. Secondaries can be read without impact on primary. This topology is previously known as *master-slave*
|
18 | 18 | * *primary*-*primary*(*source*-*source*) - operates with two primary nodes simultaneously, while other instances are configured as secondaries. This topology is previously known as *master-master*
|
19 | 19 |
|
20 | 20 | ## MariaDB Galera Cluster
|
21 | 21 |
|
22 |
| -[MariaDB Galera Cluster](https://mariadb.com/kb/en/library/what-is-mariadb-galera-cluster/) is a type of multi-primary synchronous replication which is performed at a transaction commit time, by broadcasting transaction write set to all cluster nodes for applying with the following benefits: |
| 22 | +[MariaDB Galera Cluster](https://mariadb.com/kb/en/library/what-is-mariadb-galera-cluster/) is a type of multi-master synchronous replication which is performed at a transaction commit time, by broadcasting transaction write set to all cluster nodes for applying with the following benefits: |
23 | 23 |
|
24 | 24 | * No secondary lag
|
25 | 25 | * No lost transactions
|
26 | 26 | * Both read and write scalability
|
27 | 27 | * Smaller client latencies
|
28 | 28 |
|
29 |
| -## Cluster Horizontal Scaling |
| 29 | +## Percona XtraDB Cluster |
30 | 30 |
|
31 |
| -The topologies *primary*-*secondary* or *primary*-*primary* are improved with a new horizontal scaling algorithm. The key idea of that is a new cluster member is created via cloning an existing *secondary* node. Right after the cloning procedure is completed the database on the new cluster member catches up data via binlog replay which definitely will be pretty short in time and guarantees the binlog will not expire unlike the case when the newly added node was created from scratch. Following this improvement we may guarantee cluster fast scaling with no inconsistencies that could arise since the binlog may be overwritten or expire during database cluster lifecycle before cloning. |
| 31 | +[Percona XtraDB Cluster](https://www.percona.com/software/mysql-database/percona-xtradb-cluster) (PXC) is a solution for high availability and scalability for MySQL clustering. In a nutshell, it is the Percona implementation of Galera Cluster for MySQL. PXC comes with XtraDB storage engine (a drop-in replacement of InnoDB) and follows the upstream Oracle MySQL releases very closely with the following benefits: |
32 | 32 |
|
33 |
| -## Deployment to the Cloud |
34 |
| - |
35 |
| -To get started, log in to Jelastic dashboard, import the required manifest using the link from GitHub: |
36 |
| -[https://github.com/jelastic-jps/mysql-cluster/blob/master/manifest.jps](https://github.com/jelastic-jps/mysql-cluster/blob/master/manifest.jps) |
| 33 | +* No secondary lag |
| 34 | +* No lost transactions |
| 35 | +* Both read and write scalability |
| 36 | +* Smaller client latencies |
37 | 37 |
|
38 |
| -<p align="left"> |
39 |
| -<img src="images/import-maria-mysql.png" width="500"> |
40 |
| -</p> |
| 38 | +## Deployment to the Cloud |
41 | 39 |
|
42 |
| -Or you can click the **Deploy to Jelastic** button, specify your email address within the widget, choose one of the [Jelastic Public Cloud](https://jelastic.cloud/) providers and press **Install**. |
| 40 | +To get started, you can click the **Deploy to Cloud** button, specify your email address within the widget, choose one of the [Virtuozzo Public Cloud Providers](https://www.virtuozzo.com/application-platform-partners/) providers and press **Install**. |
43 | 41 |
|
44 |
| -[](https://jelastic.com/install-application/?manifest=https://github.com/raw/jelastic-jps/mysql-cluster/master/manifest.jps) |
| 42 | +[](https://jelastic.com/install-application/?manifest=https://github.com/raw/jelastic-jps/mysql-cluster/v3.0.0/manifest.yml) |
45 | 43 |
|
46 |
| -**Note:** If you are already registered at Jelastic, you can deploy this cluster from Marketplace. |
| 44 | +If you are already registered at Virtuozzo Application Platform(VAP), you can deploy this cluster from Marketplace. |
47 | 45 |
|
| 46 | +<p align="left"> |
| 47 | +<img src="images/marketplace-w-percona.png" width="600"> |
| 48 | +</p> |
48 | 49 |
|
49 | 50 | ## Installation Process
|
50 | 51 |
|
51 |
| -In the opened confirmation window at Jelastic dashboard, choose MariaDB/MySQL replication type with appropriate cluster topology, state the *Environment* name, optionally, customize its [Display Name](https://docs.jelastic.com/environment-aliases). If required you may exclude ProxySQL layer from the cluster topology before installation, just uncheck it. Keep in mind that you won’t be able to do that later and vice versa if you disable it before installation you will not be able to add the proxy layer afterward.Then, select the preferable [region](https://docs.jelastic.com/environment-regions) (if several are available) and click on **Install**. |
| 52 | +In the opened confirmation window at VAP dashboard, choose MariaDB/MySQL/Percona replication type with appropriate cluster topology, state the *Environment* name, optionally, customize its [Display Name](https://docs.jelastic.com/environment-aliases). Then, select the preferable [region](https://docs.jelastic.com/environment-regions) (if several are available) and click on **Install**. |
52 | 53 |
|
53 | 54 | <p align="left">
|
54 |
| -<img src="images/install.png" width="500"> |
| 55 | +<img src="images/install-w-percona.png" width="500"> |
55 | 56 | </p>
|
56 | 57 |
|
57 | 58 | After successful installation, you’ll receive a number of default emails based on your environment topology with access credentials.
|
58 | 59 |
|
59 |
| -## MariaDB/MySQL Managed Hosting Business |
60 |
| - |
61 |
| -To start offering this solution to your customers please follow to [Auto-Scalable Clusters for Managed Cloud Business](https://jelastic.com/apaas/) |
62 |
| - |
63 |
| - |
| 60 | +## MySQL/MariaDB/Percona Managed Hosting Business |
64 | 61 |
|
| 62 | +To start offering this solution to your customers please follow to [Auto-Scalable Clusters for Managed Cloud Business](https://www.virtuozzo.com/application-platform/?referer=jelastic) |
0 commit comments