Module 11 — Backend workflows: automation, recursion and scale

Everything to this point ran while a user watched. Module 11 crossed the line into software that works while everyone sleeps — and into the failure modes that only exist on the other side of that line.

Backend logic is application behaviour that belongs to the system, not to a screen: nightly jobs, reactions to data changes, thousand-record updates. The moment your product needs any of these, you’ve graduated from building pages to operating software.

The curriculum

A recap of workflow concepts bridged from Module 7, then the toolkit: API workflows (server-side logic as callable units), recurring events for schedules, database triggers for change-reactions — with the warning every senior dev eventually earns about triggers cascading into triggers. Then bulk processing as a genuine engineering choice: on-a-list actions, recursive workflows (the professional’s pattern — process one, schedule the next), a process data type for tracking long-running jobs, bulk actions, and the Data API. The module closed with the grown-up trio: keeping workflows organised, debugging things you can’t see (server logs as your eyes), workload-unit considerations — compute costs money, inefficiency is a bill — and race conditions.

Try it yourself

Find the automation hiding in your app — the thing someone does manually every week. Design it as a backend job on paper: trigger (schedule? data change?), the per-item steps, what marks an item done (so a re-run doesn’t double-process), and what the log line says. That last question — how will I know what happened? — is the one that separates hobby automation from production automation.

This skill in the AI era

Queues, idempotency, retries, race conditions: this is distributed-systems thinking with the jargon removed, and it transfers to serverless functions and scheduled jobs without translation. When Claude Code writes our background jobs, the review questions come straight from Module 11 — what happens on re-run, on overlap, on failure halfway? Builders who ask those questions ship automation that holds; builders who don’t, ship time bombs. More on the transition.