11 videos 📅 2025-01-06 09:00:00 Asia/Brunei
2:33
2025-01-06 13:08:28
3:21
2025-01-08 09:13:02
4:34
2025-01-08 09:31:44
22:26
2025-01-08 09:34:32
22:27
2025-01-08 10:16:32
24:59
2025-01-08 11:36:15
6:37
2025-01-08 14:09:18
17:55
2025-01-08 18:20:43
16:28
2025-01-08 18:20:43
34:39
2025-01-08 21:21:43
34:51
2025-01-08 21:21:44

Visit the Kafka for Administrator course recordings page

United Arab Emirates - Kafka for Administrators

                WEBVTT

00:00:30.580 --> 00:00:38.080
So memq has been built on top of Kafka by the Pinterest.

00:00:38.880 --> 00:00:44.660
So they were trying to do the large file management using Kafka.

00:00:45.840 --> 00:00:54.200
So basically like which is a better management pops up platform compared to Kafka which

00:00:54.200 --> 00:01:01.060
basically like saying that it can handle more GB of traffic and with better file management.

00:01:01.160 --> 00:01:05.580
So if you see this memq, memq internally uses Apache Kafka.

00:01:10.820 --> 00:01:12.680
Any questions or any clarifications still?

00:01:12.740 --> 00:01:14.620
Any doubts till now?

00:01:14.800 --> 00:01:21.000
One is like one of the architecture of the Pinterest.

00:01:21.560 --> 00:01:27.700
So they were actually using large file management, so which they usually get it to Kafka and

00:01:27.700 --> 00:01:30.080
then send it to S3 and kind of manage it.

00:01:30.420 --> 00:01:33.300
This one is not solving their problem.

00:01:33.840 --> 00:01:40.900
What they did is like they developed the memq, memq is on top of Kafka which handles

00:01:40.900 --> 00:01:42.840
it better in terms of storage and all those.

00:01:43.420 --> 00:01:49.400
So this is developed by Pinterest because they were having issues in terms of managing

00:01:49.400 --> 00:01:53.780
the large files using the pops up model.

00:01:54.360 --> 00:02:04.600
What they did is on top of this Kafka framework they added the storage.

00:02:06.080 --> 00:02:09.320
You can add Amazon S3 or GCP or anything.

00:02:11.380 --> 00:02:16.880
Now this is managed by itself in the memq.

00:02:18.180 --> 00:02:23.000
So you can go through this whenever you have some time to understand, if you want to

00:02:23.000 --> 00:02:26.960
better understand how the other things will look.

00:02:28.420 --> 00:02:32.120
Similar to what we have Ukip or they have NetE which handles all this stuff.

00:02:33.040 --> 00:02:38.940
There are n number of things that came on top of Kafka, but Kafka on a core.

00:02:45.860 --> 00:02:47.160
Any other questions?

00:02:48.240 --> 00:02:48.760
No.

00:02:50.160 --> 00:02:54.020
And with that, I think most of the topics are discussed.

00:02:54.580 --> 00:02:59.900
I just sent you the chart like where the whole set of topics that we are discussing.

00:03:00.620 --> 00:03:01.520
You can go through them.

00:03:01.700 --> 00:03:06.020
You can see any one of them you want to go again, I can go through it.

00:03:06.020 --> 00:03:09.460
Most of the things we have covered.

00:03:17.880 --> 00:03:24.620
What is the traffic usually you have any idea like in terms of input traffic?

00:03:25.100 --> 00:03:35.740
You see here in 2020 they have a peak of 25 GB inbound and 50 GB of outbound from

00:03:35.740 --> 00:03:38.880
For this they have almost 50 clusters.

00:03:39.100 --> 00:03:42.620
It's very similar to e-commerce.

00:03:44.120 --> 00:03:49.340
But I think this is more of a social media right?

00:03:49.680 --> 00:03:54.740
They got more data that is not structured.

00:03:57.040 --> 00:03:59.840
All these small forms and payments.

00:04:04.520 --> 00:04:05.600
All the files.

00:04:19.740 --> 00:04:23.900
Even if you put it in a topic, you need to scan right?

00:04:24.020 --> 00:04:25.540
You need to make sure it's not a virus.

00:04:32.820 --> 00:04:36.320
They have one point which says they usually use their drives.

00:04:36.980 --> 00:04:42.100
Then they switch it to SSDs for better increase of their operations.

00:04:44.720 --> 00:04:49.660
They talk about the rebalancing, how they do the rebalancing, how it improves.

00:04:50.980 --> 00:04:54.700
And also the message format conversions like one format, other format.

00:04:54.700 --> 00:04:57.500
They are actually on AWS.

00:04:57.940 --> 00:05:05.940
So it is a good read to understand the cause, the data associated with that.

00:05:06.280 --> 00:05:09.200
And they talk about the ISRs, how they replicate.

00:05:10.440 --> 00:05:12.720
Most of the things we have discussed are there.

00:05:13.320 --> 00:05:19.420
But you can understand how that specific use case is having problems on how they

00:05:19.420 --> 00:05:20.140
solve it.

00:05:20.140 --> 00:05:22.720
And how they created a new main queue.

00:05:26.700 --> 00:05:29.740
I'll just send you the name.

00:05:33.460 --> 00:05:36.000
There's no exam vouchers for this right?

00:05:37.220 --> 00:05:39.180
There's no exam vouchers right?

00:05:39.440 --> 00:05:39.800
Which one?

00:05:40.020 --> 00:05:41.640
Exams vouchers.

00:05:43.700 --> 00:05:44.540
No right?

00:05:45.200 --> 00:05:45.640
No.

00:05:47.460 --> 00:05:48.480
I need to ask.

00:05:49.460 --> 00:05:51.180
Is there any certification for this?

00:05:52.160 --> 00:05:54.340
Do you have any certification for this class?

00:05:56.300 --> 00:05:57.960
We don't have right?

00:06:00.900 --> 00:06:04.980
Do we have any certification kind of thing that says that they...

00:06:08.620 --> 00:06:12.380
I will show you the e-certificate after the thing.

00:06:13.320 --> 00:06:15.080
Here you do some survey right?

00:06:16.180 --> 00:06:16.580
Yeah.

00:06:17.660 --> 00:06:18.320
Send it, send it.

00:06:18.360 --> 00:06:19.380
That's all we want to know.