Background jobs 101: building reliable apps with Inngest
summary
Shows how moving non‑blocking tasks into background jobs with inest cuts latency and adds reliability: wrap functions exposed as HTTP endpoints, emit user.signup events, and let inest invoke functions so the request path stays fast. Demonstrates a drip campaign coded with step.sleep to pause 4 days, conditional waiting for a booking.created event, automatic retry with incremental backoff on failures, a dev server dashboard showing attempts and logs, and successful recovery by retriggering events.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 2:27The problem with sync code
- 7:24Introducing Ingest
- 11:26Advanced workflow patterns
- 15:28Beyond simple emails
- 17:52Live demo and error handling
- 20:09Conclusion and final thoughts
related talks
44mMaking apps seem faster without optimizing
38mProcrastination as a Service: Caching and Queueing
18mAn Auto-Documenting Event-Driven Architecture Using Async API and Inngest
28mIDPs For The Rest of Us: Maximizing Impact When You Aren't a Tech Giant
24mDriving Adoption by Generating High Value Notifications in Backstage
23mUser Initiated Data Transfer Jobs
26mDivide & Collaborate: Creating Scalable and Healthy Backstage Ba...
55mCode the future, now