WEBVTT - This file was automatically generated by VIMEO

0
00:00:07.600 --> 00:00:10.400
Welcome back guys to the conclusion section. And in

1
00:00:10.400 --> 00:00:14.500
 this video avoid going to compare cope and

2
00:00:14.500 --> 00:00:17.300
 mqtt communication protocol. So guys,

3
00:00:17.300 --> 00:00:18.600
 let's get started with that.

4
00:00:20.700 --> 00:00:23.300
So firstly we will talk about message size

5
00:00:23.300 --> 00:00:27.400
 versus message over at here. We have four communication

6
00:00:26.400 --> 00:00:30.000
 protocols the cope mqtt. Amq

7
00:00:29.600 --> 00:00:32.500
 and HTTP the cope and

8
00:00:32.500 --> 00:00:35.300
 mqtt has been discussed properly in the course

9
00:00:35.300 --> 00:00:38.800
 and HTTP is a generic protocol.

10
00:00:38.800 --> 00:00:40.900
 You guys can search on the internet so

11
00:00:42.200 --> 00:00:46.500
Here we will see here. The core messages smaller

12
00:00:45.500 --> 00:00:49.100
 as compared to the other and message

13
00:00:48.100 --> 00:00:51.400
 overhead is also lower as compared

14
00:00:51.400 --> 00:00:54.700
 to the other mqtt comes in the mediocre list

15
00:00:54.700 --> 00:00:55.800
 as compared to the

16
00:00:56.900 --> 00:01:00.200
HTTP and amqp but

17
00:00:59.200 --> 00:01:03.000
 if we see the HTTP have

18
00:01:02.200 --> 00:01:06.100
 a bigger message size capacity, but message overhead

19
00:01:05.100 --> 00:01:08.100
 is also higher mean you can

20
00:01:08.100 --> 00:01:12.000
 say that message size is directly how

21
00:01:11.300 --> 00:01:15.300
 you can say that directly proportional to the message overhead

22
00:01:14.300 --> 00:01:17.400
 if your messages increase then message overhead

23
00:01:17.400 --> 00:01:18.500
 is also increase

24
00:01:19.200 --> 00:01:22.900
So cope and mqtt is a good to go which minimize

25
00:01:22.900 --> 00:01:25.600
 the overhead as compared to the HTTP and

26
00:01:25.600 --> 00:01:26.600
 the amqp.

27
00:01:28.200 --> 00:01:31.500
And in the next we are going to compare the

28
00:01:31.500 --> 00:01:35.400
 power consumption versus the resource requirements as compared

29
00:01:34.400 --> 00:01:38.200
 to the previous slide. Same cope

30
00:01:37.200 --> 00:01:41.600
 uses the low power and less

31
00:01:40.600 --> 00:01:43.400
 resources as compared to

32
00:01:43.400 --> 00:01:46.800
 the other and the mqtt comes in the mediocre list where

33
00:01:46.800 --> 00:01:49.600
 it consume a little bit more power as

34
00:01:49.600 --> 00:01:52.700
 compared to the core but smaller more resources

35
00:01:52.700 --> 00:01:55.700
 as compared to that go but the HTTP

36
00:01:55.700 --> 00:01:58.300
 and amqp is on the higher list

37
00:01:58.300 --> 00:02:01.000
 which consumes the most more power and the more

38
00:02:01.600 --> 00:02:04.000
 resources as compared to the mqtt and the oh

39
00:02:05.800 --> 00:02:08.500
and in the second last we are

40
00:02:08.500 --> 00:02:11.200
 going to compare the protocol with the bandwidth versus

41
00:02:11.200 --> 00:02:14.700
 the latency the same cope and mqtt have a

42
00:02:14.700 --> 00:02:17.300
 lower latency and the lower usage of bandwidth as

43
00:02:17.300 --> 00:02:20.600
 compared to the HTTP. It means where we

44
00:02:20.600 --> 00:02:23.900
 have a slow internet connection and the

45
00:02:23.900 --> 00:02:26.300
 very limited bandwidth just like in a rural

46
00:02:26.300 --> 00:02:28.500
 areas where we have a edge or you can say that

47
00:02:29.300 --> 00:02:32.600
GPRS actually many guys would many

48
00:02:32.600 --> 00:02:35.700
 guys don't know about these word because now we

49
00:02:35.700 --> 00:02:38.400
 are living in the era of 5G and

50
00:02:38.400 --> 00:02:41.400
 60 and maybe in the some years

51
00:02:41.400 --> 00:02:44.600
 next. We are going to talk about this as seven G

52
00:02:44.600 --> 00:02:47.500
 and 80, so I'm talking about the

53
00:02:49.400 --> 00:02:51.000
it's around the 2000.

54
00:02:52.800 --> 00:02:55.600
That I am talking about the edge and the GPR so

55
00:02:55.600 --> 00:02:58.500
 that I maybe still there are

56
00:02:58.500 --> 00:03:01.600
 many Under 12 countries and many locations where we have the latency

57
00:03:01.600 --> 00:03:04.100
 and the bandwidth issues. So the cope and

58
00:03:04.100 --> 00:03:07.800
 mqtt works very well on these internet connectivity

59
00:03:07.800 --> 00:03:11.100
 and that's why these two communication

60
00:03:10.100 --> 00:03:13.600
 Protocols are good for iot notes

61
00:03:13.600 --> 00:03:13.700
 because

62
00:03:14.500 --> 00:03:18.300
they didn't consume too much bandwidth and it works

63
00:03:18.300 --> 00:03:20.100
 perfectly on the lower latencies.

64
00:03:21.600 --> 00:03:25.200
And finally, we need to talk about the reliability qos

65
00:03:24.200 --> 00:03:29.200
 versus the interoperability. So mqtt

66
00:03:27.200 --> 00:03:30.700
 is a more reliable

67
00:03:30.700 --> 00:03:33.500
 and quality of services are good,

68
00:03:33.500 --> 00:03:36.400
 but there's no interoperability with other.

69
00:03:37.300 --> 00:03:41.100
Communication protocols. So cope and

70
00:03:41.100 --> 00:03:45.000
 HTTP is compatible interpretable with other Technologies,

71
00:03:44.300 --> 00:03:47.400
 but the reliability

72
00:03:47.400 --> 00:03:50.500
 is not good as like mqtt. So

73
00:03:50.500 --> 00:03:53.600
 here I'm qtt is on

74
00:03:53.600 --> 00:03:56.200
 number one, but the disadvantage is

75
00:03:56.200 --> 00:04:00.000
 that that it's not interoperable with existing web Technologies

76
00:03:59.100 --> 00:04:01.800
 our web protocols.

77
00:04:03.500 --> 00:04:06.600
So guys in the next video, we're going to conclude all

78
00:04:06.600 --> 00:04:10.100
 the stuff where I am going to talk about myself.

79
00:04:11.600 --> 00:04:14.300
By which means you can contact with me, so I see

80
00:04:14.300 --> 00:04:16.200
 you in the next video. Have a good day, bye-bye.
