Spike: Determine if/how the template could support background jobs

[sawyerh]

What's the task?

It's common for projects to require background jobs (i.e. for ETL pipelines, processing file uploads, etc). How could a team using the template create a background job? What is currently missing that would need to be added in order to support this use case? Does Next.js play a role at all?

Some additional context from @lorenyu:

• From an infra perspective, it wouldn't require much. Just needs an entry point / command to run. Ideally using the same Docker image, so we don’t need another build repository and task definition. From an infra perspective, whether it’s separate package.json files or one, doesn’t really matter, as long as the docker build process builds all of them.

Related:

• Trigger jobs on document uploads template-infra#509

[coilysiren]

Grants.gov uses AWS step functions for background jobs, example: HHS/simpler-grants-gov#1604