Improving app performance by using background jobs
summary
Build speed and reliability by moving nonblocking tasks to background jobs and using Ingest durable workflows to run functions asynchronously via HTTP endpoints. Code triggers an event that fires two functions in parallel, Ingest retries until success and keeps detailed logs, and workflow steps can sleep 4 days for drip campaigns without running a server process. Examples include MailChimp/Resend integrations, conditional followups based on a booking event, and mixing TypeScript Python and Go functions.
AI-written summary · about
chapters (11)
- 0:00Background jobs intro
- 3:53Blocking code in APIs
- 5:17Move tasks to background jobs
- 7:26Durable workflows with Ines
- 8:30Adding Ines to project
- 10:58Reliability in Ines
- 11:40Schedule multi-step processes
- 13:07Dynamic workflows by user
- 14:32Beyond emails with Ines
- 15:55Reliability in production
- 17:22Conclusion
related talks
39mAsynchronous Processing for Fun and Profity
46mBackground Jobs — What to Implement Them With and Why We Chose Temporal
27mEmpowering Resilient Scalability: The Power of Choreography in Distributed Systems
27mWorkflows@Facebook: Powering Developer Productivity and Automation at Facebook Scale
42mHow to build distributed systems in JavaScript
01h 38mBuilding Reliable Distributed Systems
52mEvent Driven Workflows
25mApplying CloudEvents to Level up Application Communications