Why and how to transform a REST API into a Data Streaming API
summary
Argues that polling is dead for many apps and shows concrete alternatives: compare Server-Sent Events vs WebSockets, webhooks and PubSubHubbub, with the key data point that Zapier found 98.5% of polls wasted. Demonstrates a live pipeline using Streamdata.io as a proxy that polls once, sends incremental updates with JSON-Patch, and streams via EventSource to a Node client driving an AR drone on BitcoinAverage prices — demo mostly works though the drone behavior is jittery.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:05MODERN TIMES
- 1:45ANIMATION IS THE KEY...
- 2:00BECAUSE OF EVOLUTION
- 2:34USER INTERFACE
- 4:09REFRESH BUTTON IS EVIL
- 4:20REAL-TIME USER EXPERIENCE
- 5:02F.O.M.O (FEAR OF MISSING OUT)
- 5:32SOLUTIONS FOR REAL-TIME APPLICATIONS
- 14:14CONSUMER SETUP
- 18:10KNOWN ISSUES
- 20:26CHECK LIST
- 28:32WEBHOOKS PROS AND CONS
- 29:38WEBHOOK VS PUBSUB
- 31:34PUSH TECHNOLOGIES
- 32:27PROTOCOLS
- 33:06CONFIGURATION
- 34:06MESSAGES FORMAT
- 34:51IMPLEMENTATION WebSockets
- 36:53LOST IN CONNECTION
- 39:07MOBILE BROWSER SUPPORT
- 39:19PERFORMANCES
- 41:18STREAMDATA.IO
related talks
28mThe End of Polling
26mThe end of polling
14mStreaming the Web (it's not what you think)
29mAPIs and Event Streaming Dualty
23mDeliver real-time data to customer using Streaming APIs
04mSneak peek into the API world outside REST
21mREST APIs vs. Data Streams: Which Is Right for Your Business?
40mBuilding an open Data Stream using Node.js, VanillaJS and Ably