WEBVTT

00:04.400 --> 00:05.060
Let's proceed.

00:05.130 --> 00:10.870
Now let's talk about different Gloucester's, of course, if your company is really large and they've

00:10.880 --> 00:18.080
spread all over the world, it is a really nice idea to create multiple clusters in different countries

00:18.080 --> 00:20.630
or on different continents or something like that.

00:21.110 --> 00:28.370
And each cluster will be actually separate entities with their own brokers, with own producers and

00:28.370 --> 00:29.080
consumers.

00:29.480 --> 00:36.320
Also, zookeeper is required in every class, and you may create as many clusters as you need, but

00:36.320 --> 00:37.640
now you may ask the question.

00:37.760 --> 00:41.510
But what about data synchronization between different clusters?

00:41.720 --> 00:42.920
Of course it is possible.

00:42.920 --> 00:49.970
If you need it and you are able to stop Merian between different clusters you are even able to accomplish

00:49.970 --> 00:55.400
following the scenario when Gloucester's will be fully in sync with each other.

00:55.790 --> 00:59.510
But what is the idea behind creation of different Gloucester's?

00:59.690 --> 01:00.470
Let me explain.

01:00.920 --> 01:08.240
For example, there are two clusters, one in USA and one in Europe, and producers that are located

01:08.240 --> 01:14.370
closer to the cluster in the US will produce messages to that cluster afterwards.

01:14.390 --> 01:21.620
Those messages will be synched with cluster are located in Europe and if there was some consumer located

01:21.620 --> 01:25.880
in Europe, it will connect to the closer to IT class located in you.

01:26.150 --> 01:32.570
And in such case, a message that was produced in one of Gloster will be read in another cluster, thanks

01:32.570 --> 01:34.930
to Merian between two different Gloucester's.

01:34.970 --> 01:40.790
And of course, such separation and creation of two different clusters will reduce total load and will

01:40.790 --> 01:42.010
increase efficiency.

01:42.500 --> 01:48.490
If you, of course, don't require any Mehring, you are able to create completely separate clusters

01:48.500 --> 01:49.700
in different regions.

01:50.390 --> 01:52.580
That's all what I wanted to tell you about Gloucester's.

01:52.580 --> 01:59.480
And please keep in mind that every cluster is a separate entity and it requires a separate brokers and

01:59.480 --> 02:00.890
the separate Ozaukee process.

02:00.890 --> 02:06.920
And if you need to, producers may produce messages even to different clusters and consumers may consume

02:06.920 --> 02:08.960
messages also from different clusters.

02:09.380 --> 02:10.210
Okay, let's proceed.

02:10.220 --> 02:16.250
And next, let me explain to you, which both are used by default to when you start as Okpara and Kafka

02:16.250 --> 02:17.620
Broecker on computer.

02:17.840 --> 02:18.950
So see you next by.