HTTP, WS & MQTT for IoT

[@manasXP]

Very informative. I greatly enhanced my knowledge of IoT by just watching this lecture and hope to see rest of the series. Where to use HTTP(s), Websocket and MQTT is something I learnt today.

[@techbeast-org]

Glad it was useful 😊 keep supporting us !!

[@andreiasimov33]

Amazing explanation, really glad having found this video. Everything is much much more clearer now!! Thanks a lot man!

[@thiyaguextrovert]

Clearly explained on the difference between http, ws and mqtt protocol. It would be helpful if more information shared on mqtt protocol. Thanks.

[@mohamadmansoor3933]

how is ws not blocked by firewalls? I mean if there any firewall that will close connection over its port, it is then blocked. using TCP is all about security.

[@daminda33]

Thank you. HTTP and WS were well explained. It would have been better if you have explaine how MQTT helps to have a better battery life and its low bandwidth consumption. Appreciate your effort.

[@fayezalle43]

Thank you.. Very clear explanation.

[@techbeast-org]

Thanks for the support !! Pls do share and subscribe us😄

[@AnkushSharma-xn4hf]

How MQTT work in the UPI when we pay online to any platform like phonepay & paytam etc

[@agon4131]

It would be cool, if you can make a example for each protocol using Arduino & Sim900. And than compare the used bandwith.

[@srodrmmabet6381]

Excellent vid and explanations.. thanks!

[@techbeast-org]

Thanks , keep supporting :)

[@shahriartasnim9957]

very good demonstration. Keep going

[@Bimal.Kumar.Jena.7]

A great introduction to IOT

[@eduardogil1775]

Great explanation, thnx for sharing! 👍🏼

[@techbeast-org]

Glad it was helpful!

[@ihsanerayketenci]

11:55 you said that mqtt is over tcp/ip. actually did you mean under tcp/ip? because i understandtd that from top to bottom, htpp to tcp/ip it covers one by one and i understand that http is more wider area and tcp/is less wide and the mqtt is the least wide in these perspective. i mean mqtt should work under tcp/ip should not over?

[@techbeast-org]

Thanks for your support ! Mqtt utilizes TCP/IP as its underlying transport mechanism for communication. Hence we say that MQTT is over TCP/IP. Hope it helps !!

[@ihsanerayketenci]

@@techbeast-org got it. Thanks. Have fun!

[@christiankijuki1309]

Hi, please can i have this presentation please

[@nandhu7039]

Explanation very good 👏

[@tivideosAZ]

Great explanation on MQTT with practical examples of actual implementation scenarios. I would like to see the extension of the same scenerio with actual code, like the API calls on the Publisher end and the subscriber ends, if possible..then the implementation concept will be very clear to anyone who wants to create workable solutions to publish data from an MQTT Publisher and subscribe and receive the same (published data) by the client..actual code.. is it written in script form?

[@fawzilinggo]

hello i am interested in your explanation about iot. I asked permission to take some pictures from this video for my presentation assignment. I will include the source, which is from your KZbin video. Thank you

[@techbeast-org]

Gald that you found this video helpful !! You can include the source of our contents in your presentations :) thanks

[@adamblance3346]

Very useful, thanks!

[@MrBrain619]

Is fixed Ip a must on mqtt iot?

[@techbeast-org]

It always depends on our use case. Normally in production, mqtt server will have a fixed IP address or a domain name to connect , hope it helps !!

[@mohamadmansoor3933]

No, because the TCP/IP frame doesn't include only IP address but also a mac address but broker ip address should be constant or else you would like to configure your publisher every time the broker IP address changes. and why your clients or pub/sub(s) don't need to have static ips? because there is almost no security levels in mqtt so anyone can publish a message on a topic and anybody can subscribe to any topic or a full tree without knowing each other.

[@mohamadmansoor3933]

I am talking about the resource-constrained user version of mqtt absolutely, if it is using SSL/TLS there is a big difference in security levels.

[@AshrafulHussainKhan]

Interesting question. Broker: The broker IP address to be fixed if you are using the global IP of the broker. In case you don't worry about the IP address of the broker then bind the public IP of the broker with a DNS address and use the DNS address to connect to your broker. Client: There is no requirement of the fixed IP in the client system.

[@rasikakshirsagar5563]

Thank you for info !

[@techbeast-org]

Thanks , please do subscribe and support us !!

[@miger-lk]

Great explanation brother.

[@RayTampan69]

great video, nice

[@sridharg5319]

HI 6:13 ARE YOU TAMIL ?

[@RishiRajKoul]

very nice conent

[@techbeast-org]

Thanks :) Keep supporting us !!