Background jobs for AI workloads: when a run should not hold a request open
When an AI run belongs in a request and when it belongs in a job, and how 10xGraph runs jobs as a thin TaskIQ layer with a worker, a scheduler and the same auth.
What runs around your AI code: the infrastructure 10xGraph ships
Follow one request through 10xGraph: API server, access control, data and state, background jobs, observability and deploy. What you write and what runs for you.