API Maker

The backend engine for the AI era

Playlist · 4 videos · 24 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

  1. 5:101. Events

    Event-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. 5 min 9 chapters Episode 21
  2. 4:352. WebSockets

    WebSockets 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. 5 min 9 chapters Episode 22
  3. 7:113. Schedulers

    Schedulers: 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. 7 min 13 chapters Episode 23
  4. 6:484. Schedulers

    Schedulers on Every Server and Distributed Locks with Redis

    Run a scheduler on every server, or in every runner of every server, and share the work between the runs with g.req.scheduler. Then keep each piece of work to one run with g.sys.system.getLock and releaseLock: an invoice sent once across two servers, three payments at a time, holds that end by themselves, in all eight languages. 7 min 10 chapters Episode 77