LOOK UP WHEN NEEDED
Background job
Work performed without holding the user in a foreground flow.
An everyday example
Prepare a report after the request is submitted.
See how these concepts connect
The frontend requests through an API; the backend applies rules and accesses data. Results return in the reverse direction.
Where this term is useful
These are related contexts, not prerequisites.
Back in the project
When it comes up: When organizing services, background work, and concurrent use.
What to do next: Map the current request path and validate a minimal flow before adding complexity.
Open the related method and stepsWhat can this analogy leave out?
Multiple services add coordination cost; serverless still uses servers and incurs charges.
Everyday examples explain roles and relationships; actual behavior follows the tool, language, or platform.