System design · Patterns: the problems hiding inside most prompts

Long-running jobs: answer now, finish later

Work that takes longer than a user will hold a request open must leave the request path, and the design that replaces it (a job record, a queue, a worker pool and a way to report status) has a handful of failure modes that decide the grade.

21 min read Full lesson in the app Patterns: async job, visibility timeout, idempotent worker

What you'll be able to do

Before this: queues-and-backpressure

Log in to read the rest of this lesson

Work that takes longer than a user will hold a request open must leave the request path, and the design that replaces it (a job record, a queue, a worker pool and a way to report status) has a handful of failure modes that decide the grade. This walkthrough runs about 21 minutes, with runnable code you can edit and re-run as you read. A new account gets 7 days of Pro free, no card required.

Log in to continue

The first module of every track is free to read on the web: see what's open in System design.