Webhook vs. Polling
Noun · Comparison · Development
Definitions
Two approaches to getting updates: polling (repeatedly asking 'anything new?') vs. webhooks (getting called when something happens). Polling is simpler; webhooks are more efficient. The 'checking the mailbox every 5 minutes' vs. 'getting a doorbell' debate.
In plain English: Two ways to get updates: polling keeps asking 'got anything new?' over and over, while webhooks wait quietly and only get notified when something actually happens. Webhooks are usually more efficient.
Related Terms
- Webhook
- WebSocket
- server-sent events
- ADR
- Consume
- Decentralization
- Distributed Systems
- Event
- Figure
- Framework
- Function Handle
- Game Loop
- HPC
- Instruction Set
- Interoperability
- Message Passing
- Offline-First
- Payment Gateway
- Sharding
- State Machine
- System Design
- Vapi
- Strangler Fig Pattern
- Event Sourcing
- Saga Pattern
- Hexagonal Architecture
- Backoff
- Leader Election
- Write-Ahead Log
- Sidecar
- Init Container
- Change Data Capture
- Monorepo
- Dead Letter Queue
- Greenfield
- Von Neumann Bottleneck
- Finite State Machine
- Slowly Changing Dimension
- Medallion Architecture
- Idempotent Pipeline
- Windowing
- Watermark
- Local-First Software
- API Gateway Pattern
- Glue Code
- Long Polling
- Observer Pattern
- Adapter Pattern
- Repository Pattern
- Pub/Sub
- Partial Application
- Immutable Deploy
- Feature Toggle
- Dependency Graph
- CTE
- Bounded Context
- Aggregate
- CQRS
- Clean Architecture
- Anti-Corruption Layer
- Cache Invalidation
- Sliding Window
- Second System Effect
- Dark Debt
- Backpressure
- GraphQL Fragment
- Consumer Group
- Inbox Pattern
- Backend for Frontend
- API Composition
- Regex
- Frameworks vs Libraries
- Fullstack Framework
- GUI Framework
- Master-Slave
- Message Bus
- Multi-Tenant
- Pull Model
- Request Pipeline
- Unidirectional Data Flow
- Communication Bus
- Cross-Service