Webhook vs Polling
Two ways for one system to learn that something changed — and how to decide which pattern fits the situation.
Explain a technical trade-off clearly enough to decide.
Start with the problem, explain the mechanism simply, then surface the trade-offs and failure modes that change the choice.
How does one system learn that something changed in another?
There are two common patterns: either the first system keeps checking, or the second system sends a message when the change happens.
“I’ll keep asking.”
System A checks System B every so often: “Anything new?”
“Tell me when it happens.”
System B sends a message to System A when the event happens.
One change, two ways to learn about it
Which one would I use?
If updates do not need to be immediate
Checking every few minutes may be perfectly enough.
If another system should react quickly
A notification when the event happens is usually a better fit.
If missing an update would be costly
Sometimes webhooks handle fast updates while periodic checks are kept as a safety net.
One level deeper: what can go wrong with webhooks?
A webhook is still just a request between systems. It can fail, arrive late, or be sent more than once.
In real integrations, the receiving side often needs to handle retries and duplicate events so that the same business action is not performed twice.
That is why “the source sent a webhook” is not the same as “the business operation definitely happened exactly once.”
Technical wording, if you want it
Polling: the client sends scheduled requests to read the latest state.
Webhook: the source sends an HTTP request to a predefined receiver when an event occurs.
The receiver may need validation, monitoring, retry handling and duplicate protection, depending on the business operation.
Need this kind of systems thinking on your team?
If the role needs someone who can translate technical mechanisms into clear, testable decisions, let’s talk.