Playlist · 3 videos · 15 min
Events, WebSockets and schedulers
React to anything with events, push live data over WebSockets from the same server as your APIs, and run jobs on a clock without a cron server.
The videos of this playlist
4:231. EventsEvent-Driven APIs: React to Saves, Code and HTTP Calls
Code that reacts to what happens: after a save, from your code, or over HTTP, without a queue or a worker to run. Follow the events of Calm Home: an order saved, a row written behind the answer, a chain of events emitted from code, and a careless loop stopped by API Maker.
4:062. WebSocketsWebSockets Without a Realtime Server: Push Live Data from Your APIs
Live data for your apps from the same server as your APIs: a save, a status, pushed the moment it happens. Follow Kabir, a customer of Calm Home: one WebSocket, his orders live, a status pushed from code with emitEventWS, a rule for each subscription, and how far it scales.
6:103. SchedulersSchedulers: Cron Jobs Without a Cron Server
Code that runs on a clock: every minute, every night, or on weekdays at nine. No cron server, no double runs, and every run on record. Build a low stock alert for the buyers of Calm Home with intervals and cron expressions, run it now, pause it, give it a timeout, and see it run once per cluster with failover.