WEBVTT

00:00:00.000 --> 00:00:05.920
 Welcome to Jelastic. In this video, you will learn how to create SQL or NoSQL database clusters in

00:00:05.920 --> 00:00:11.040
 Jelastic POS with help of auto-clustering functionality. Log into your Jelastic account

00:00:11.040 --> 00:00:15.840
 and open the new environment creation wizard. There are two groups of database software stack

00:00:15.840 --> 00:00:24.160
 templates with built-in auto-clustering. These are SQL that comprises MariaDB, MySQL, PostgreSQL,

00:00:24.160 --> 00:00:32.720
 and NoSQL group represented by MongoDB and Couchbase. All of these stacks can be automatically

00:00:32.720 --> 00:00:38.800
 clusterized with the auto-clustering switch. Let's take a closer look at them. Database clusters can

00:00:38.800 --> 00:00:43.440
 be deployed with different topologies depending on the replication scheme you choose. For the

00:00:43.440 --> 00:00:49.440
 MariaDB database, there are three schemes available, primary-primary, primary-secondary,

00:00:49.440 --> 00:00:59.200
 and Galera cluster. For MySQL, there are two schemes available, primary-primary, and primary-secondary.

00:01:03.360 --> 00:01:09.280
 By default, all of these topologies include a proxy SQL layer. It serves as a database cluster

00:01:09.280 --> 00:01:14.960
 entry point, and it is used to do a smart distribution of queries between cluster members.

00:01:14.960 --> 00:01:19.600
 To add the failover and query control, to see your query traffic almost in real time,

00:01:19.600 --> 00:01:24.640
 without a need to collect the data first, to execute graceful failovers and switchovers

00:01:24.640 --> 00:01:32.480
 between cluster nodes. If required, the proxy SQL can be disabled, but in this case you should take

00:01:32.480 --> 00:01:38.080
 care of how to properly distribute read and write requests among cluster nodes. Let's create the most

00:01:38.080 --> 00:01:44.480
 complicated replication topology, such as MariaDB Galera cluster. Waiting for MariaDB Galera

00:01:44.480 --> 00:01:50.080
 environment to be created, let's check the rest of available automatic database clusters, MongoDB,

00:01:53.280 --> 00:02:02.400
 Couchbase, and PostgreSQL databases, simply hovering mouse over the auto-clustering tooltip question mark.

00:02:04.880 --> 00:02:10.000
 Normally, database cluster manual installation and configuration takes hours or even days

00:02:10.000 --> 00:02:15.120
 depending on the required topology. In Jelastic it takes several minutes, regardless of the

00:02:15.120 --> 00:02:21.280
 selected topology to be created. And as you can see, this is indeed the case. For our example,

00:02:21.280 --> 00:02:25.760
 we chose the Galera cluster, which is the most complex, and we got it in a few minutes.

00:02:27.280 --> 00:02:34.080
 It consists of three nodes of database servers, and two nodes of load balancers as an entry point.

00:02:34.080 --> 00:02:37.840
 Jelastic POS. Simplicity that breaks free.