Passed through about 7 videos and none of them explained what the heck was the problem Webhooks solve, you did. Your explanation is clear and calm, but not too much to allow me to distract. Thank you! ✨
I've been looking for a clear explanation of how WebHooks work and how they can be used, and this video delivered exactly that. The author did a great job of explaining the concept in a concise and easy-to-understand way. Many thanks!
hey thanks for the video - I would just give you a piece of advice, music while you're speaking and drawing graphs seriously impedements learning. Hope that helps and thanks for your very clear explanation :)
Great! I’m managing a IT team for the integration of Shopify with a billing SaaS through a middleware. This has been great to a better understanding! Thanks!
So instead of an external program requesting information at regular intervals, the web hook exists internally and upon a condition send that information to the external system for greater efficiency. Correct?
Appreciate this (and your other videos) as I find them very informative. I did have a question here specifically though- this sounds awfully like Kafka events, does this mean Kafka is simply a type of Webhook?
They are somewhat different. Kafka is more analogous to publishing a newspaper (remember those?) or publishing a video to TH-cam. The event content is pushed out (to TH-cam or Kafka) and it can be consumed by other systems at some asynchronous future point in time (and the content may expire from the topic). Webhooks are more like a telephone system where the event generating system will "call" (send a message) to the subscribing system(s). It wasn't mentioned here but typically, the subscribing systems will call an API on the event-raising system providing the subscriber's API which the event publishing system should call (Basically, "when this event happens, please call me at this phone number"). It's up to the subscriber to always have this API available or (like phone voice mail), have a highly available message queue - which could be Kafka or similar. An email mailing list is also a good analogy - interested parties subscribe to an email newsletter (or whatever) and the event-originating system periodically sends out an email to all the subscribers on its list. It's up to the subscriber to receive the email. (Almost all email today is queued for subscriber retrieval on an IMAP or POP email server but this is not required. You could send and receive messages directly via the SMTP protocol without queuing.)
An API is an interface you call call to cause an action or retrieve data, A webhook is triggered by an event in a system which then can call an API. An event could be caused by an API being called.
The problem is, that webhooks are not reliable. If data consistency is critical, you have to write some mechanism for the guaranteed delivery and replicate information. But not webhooks based for sure.
You could create a webhook in our system that sends a piece of content to a search engine like algolia to be indexed when it's is published. Or have webhooks in a smart home app the switches on the heating when a theromastat reaches a temperature
Passed through about 7 videos and none of them explained what the heck was the problem Webhooks solve, you did. Your explanation is clear and calm, but not too much to allow me to distract. Thank you! ✨
Instead of me constantly asking, “is it done yet?”,
you tell me when it’s done.
i agree :)
i was polling entire youtube to finally find this simple one. You need webhooks to tell us back.
A complicated subject is explained in a very simple, concise yer in style, very well presented too. It is very comfortable watch too.
Thank you tech can be quite difficult to explain
I've been looking for a clear explanation of how WebHooks work and how they can be used, and this video delivered exactly that. The author did a great job of explaining the concept in a concise and easy-to-understand way. Many thanks!
Nicely presented - thank you John!
Brilliantly explained, good video quality, music, designed. You nailed it. Kudos! 👏
hey thanks for the video - I would just give you a piece of advice, music while you're speaking and drawing graphs seriously impedements learning. Hope that helps and thanks for your very clear explanation :)
The analogy at beginning was amazing. Thank you!
A very good quality content. Simple and concise. Thank you!
Nice video that simplifies the subject. Good analogies and I'm an Iron Maiden fan as well!
I love the way you explained that. !
Thank you for the clear explanation. Your help is much appreciated!
Thank you for the thorough explanation!
Great! I’m managing a IT team for the integration of Shopify with a billing SaaS through a middleware.
This has been great to a better understanding! Thanks!
Keep sharing such contents
I'll try keep them coming
Love the Alexa ending :)
I cam up with the Alexa ending while walking the dog. It worked out fortunately
i appreciate the Maiden example
So instead of an external program requesting information at regular intervals, the web hook exists internally and upon a condition send that information to the external system for greater efficiency. Correct?
Callback over the internet, simple
very well explained, This is what I was looking for ..
Amazing video! Thank you for making this
Really awesome explanation!
thanks for this video! one suggestion is to lower the music volume as it is very distracting.
Great explanation...👍
Awesome video John
Thanks 👍 so glad you enjoyed it.
Great explanation!
music playing in the video makes it hard to hear sometimes :(
great explanation
thank you
Appreciate this (and your other videos) as I find them very informative. I did have a question here specifically though- this sounds awfully like Kafka events, does this mean Kafka is simply a type of Webhook?
They are somewhat different. Kafka is more analogous to publishing a newspaper (remember those?) or publishing a video to TH-cam. The event content is pushed out (to TH-cam or Kafka) and it can be consumed by other systems at some asynchronous future point in time (and the content may expire from the topic). Webhooks are more like a telephone system where the event generating system will "call" (send a message) to the subscribing system(s). It wasn't mentioned here but typically, the subscribing systems will call an API on the event-raising system providing the subscriber's API which the event publishing system should call (Basically, "when this event happens, please call me at this phone number"). It's up to the subscriber to always have this API available or (like phone voice mail), have a highly available message queue - which could be Kafka or similar. An email mailing list is also a good analogy - interested parties subscribe to an email newsletter (or whatever) and the event-originating system periodically sends out an email to all the subscribers on its list. It's up to the subscriber to receive the email. (Almost all email today is queued for subscriber retrieval on an IMAP or POP email server but this is not required. You could send and receive messages directly via the SMTP protocol without queuing.)
beautifully explained, thank you
Thank you for the information sir, on point.
I feel so happy when I come searching for some boring stuff e and get IRON MAIDEN somehow!!!! UP THE IRONS!!!
very helpful video. Thanks!
Thankyou Glad it was helpful!
very well explained
Should we write our own webhook service or use the service from the webhook providers?
Great video
Thankyou, Glad you enjoyed it!
Is it not same as Kafka Where Application pushed the message
However Webhook is based in https is my understanding correct ?
is there any possibility to remove ellipsis from PWA MicrosoftEdge?
very well explanation
Thanks its can be difficult to think of ways to explain technology
Very nice video🤗
I really appreciate the feedback
you are amazing, I liked it
Thanks you are very kind
great video! (dust your Alexa :D)
how is the webhook different to an API?
An API is an interface you call call to cause an action or retrieve data, A webhook is triggered by an event in a system which then can call an API. An event could be caused by an API being called.
The problem is, that webhooks are not reliable. If data consistency is critical, you have to write some mechanism for the guaranteed delivery and replicate information. But not webhooks based for sure.
What is a webhook example?
You could create a webhook in our system that sends a piece of content to a search engine like algolia to be indexed when it's is published. Or have webhooks in a smart home app the switches on the heating when a theromastat reaches a temperature
God bless u
❤❤❤
test comment
Great video
Thankyou glad you enjoyed it
great video