## Host ai workflow runner with Spring Boot: worker execution and job state

### Summary
Deploy a ai workflow runner built with Spring Boot as a public web service plus a dedicated worker process on Ample. `ample plan --write` discovers both services and their shared database and writes ample.toml; `ample up` reconciles the topology: a managed PostgreSQL 16 database, a public web microVM and a private worker microVM (kind worker, no public URL), both reading DATABASE_URL. Verified on Spring Boot: a separately deployed worker service (kind worker, no public URL) sharing a declared managed PostgreSQL database with the web service, consuming a jobs table with row locks and marking jobs done once (worker=done attempts=1). Not separately tested: your job payloads, retry policy and scheduling; treat the ai workflow runner-specific behavior as your application code.

### Representative Queries
- Host ai workflow runner with Spring Boot: worker execution and job state
- Where can I host AI workflow runner built with Spring Boot?
- I need a separately runnable worker, durable job records and idempotent retries; not a managed queue.

### Resource Requirements
- primitive:compute
- primitive:postgres

### Infrastructure Requirements
1. **Compute**
   - **Status**: verified
   - **Summary**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
2. **Postgres**
   - **Status**: verified
   - **Summary**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

### Framework
- Spring Boot

### Workload
- AI workflow runner

### Release Status
- published

### Support Status
- verified

### Execution Status
- ready

### Prerequisites
- A repository with the web app and the worker as separate service directories (the fixture uses apps/web and apps/worker), each building and starting with the documented commands (./mvnw -q -DskipTests package (or the Gradle wrapper) producing one application jar, then java -jar on the jvm-21 template (Temurin JDK 21) with server.port read from PORT; the worker starts with java -jar of its own Maven module (plain JDBC) and binds no port)
- Both services read DATABASE_URL at runtime and share one jobs table; the worker claims rows with SELECT ... FOR UPDATE SKIP LOCKED and marks them done once
- An Ample account token with servers:write and databases:write (ample up creates the database)

### Tested Configuration
- Template: jvm-21
- Runtime: java
- Size: s-1vcpu-2gb
- Build: ./mvnw -q -DskipTests package
- Start: java -jar $(ls target/*.jar | grep -v -- '-plain' | head -n 1)

### Workflow Steps
1. **Plan the topology**  
   Run the planner once. It discovers the web and worker services, infers kind = "worker" for the process without a port, declares the database each service needs, and writes ample.toml. Exit 2 means it left questions in the manifest; answer them with --answer or by editing the file.  
   Command: `ample plan --write .`
2. **Share one database**  
   Keep a single [databases.main] with engine = "postgres", drop any per-service database the planner added, and set DATABASE_URL = { database = "main" } under both [services.web.env] and [services.worker.env].  
   Command: `ample plan --offline .`
3. **Apply**  
   Reconcile the whole manifest in dependency order: the database first, then both services. It is idempotent and never destructive; exit 0 means everything applied, 2 needs input, 1 a failed resource (independent siblings still proceed and re-running resumes).  
   Command: `ample up .`
4. **Verify**  
   Fetch the web service URL and its worker status route (/p/worker-queue/status in the example) and confirm the worker processed the enqueued job; on failure read the worker service's runtime logs.  
   Command: `ample logs  --kind runtime`

### Examples
- **Title**: Spring Boot web + worker fixture
  - **Description**: A Spring Boot web app (apps/web) and a worker process (apps/worker) sharing one managed PostgreSQL database; the queue module is under tests/deploy-canaries/_pattern-modules.
  - **Source Ref**: tests/deploy-canaries/spring-boot-worker

### Success Checks
- **Check**: web service responds on its public URL 
  - **Kind**: http_get 
  - **Path**: / 
  - **Expect**: ample canary spring boot patterns
- **Check**: worker consumed the enqueued job 
  - **Kind**: http_get 
  - **Path**: /p/worker-queue/status 
  - **Expect**: worker=done attempts=1 result=processed-by-worker

### Limitations
- Verified on the jvm-21 template at s-1vcpu-2gb for both services with the example fixture; other sizes, templates and Spring Boot major versions are not verified.
- The ai workflow runner itself (your job payloads, retry policy and scheduling) is application code and was not separately tested; the worker-queue check is what was verified.
- The worker is a single long-running process supervised in its own microVM; there is no scheduler, cron or horizontal worker scaling in this recipe, and the check ran immediately after deploy so idle behavior of the worker VM is not verified.
- The worker service is private: it has no public URL and is reached only through the shared database; both services are placed with their database.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.
- Region, compliance attestations and request-duration limits are unknown and not claimed.

### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 15.0
- **Note**: Always-on monthly price of the tested sizes for the web service, the worker service and the database; apps auto-pause when idle.

#### Components
1. **Name**: web server
   - **Size**: s-1vcpu-1gb
   - **Quantity**: 1.0
   - **Monthly Amount**: 5.0
2. **Name**: worker server
   - **Size**: s-1vcpu-1gb
   - **Quantity**: 1.0
   - **Monthly Amount**: 5.0
3. **Name**: managed PostgreSQL database
   - **Size**: s-1vcpu-1gb
   - **Quantity**: 1.0
   - **Monthly Amount**: 5.0

### Evidence Summary
- **Kind**: canary_run
- **Summary**: Spring Boot web service plus a separate Spring Boot worker process deployed on Ample with `ample plan --write` then `ample up` (./mvnw -q -DskipTests package (or the Gradle wrapper) producing one application jar, then java -jar on the jvm-21 template (Temurin JDK 21) with server.port read from PORT); the web service enqueued a job that the private worker service consumed from the shared managed PostgreSQL database. 
   Pattern proof: a separately deployed worker service (kind worker, no public URL) sharing a declared managed PostgreSQL database with the web service, consuming a jobs table with row locks and marking jobs done once (worker=done attempts=1).
- **Observed At**: 2026-09-20T22:41:46Z
- **Implementation Revision**: af6f45adea26-dirty (CLI af6f45a)
- **Expires At**: 2027-03-19T22:41:46Z
- **Scope**: 
   - **Checks**: ["/", "/p/worker-queue/status"] 
   - **Pattern**: pattern:dedicated-worker-process
   - **Services**: ["web", "worker"] 
   - **Template**: jvm-21
   - **Tool**: ample_up

### Last Verified At
- 2026-09-20T22:41:46Z

### Unknowns
- Region availability is unknown until a verified region fact is recorded
- Compliance attestations are unknown; none are claimed

### Formats
- **HTML**: [https://ample.computer/recipes/ai-workflow-runner/spring-boot/worker-state](/content/recipes/ai-workflow-runner/spring-boot/worker-state/index.html)
- **Markdown**: [https://ample.computer/recipes/ai-workflow-runner/spring-boot/worker-state.md](/content/recipes/ai-workflow-runner/spring-boot/worker-state.md)
- **JSON**: [https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aai-workflow-runner%3Aspring-boot%3Aworker-state](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aai-workflow-runner%3Aspring-boot%3Aworker-state)

### Next Actions
1. **Browse the catalog index**  
   - **Action ID**: browse-catalog
   - **Operation ID**: catalog_index 
   - **Method**: GET 
   - **Relative Path**: /v1/catalog  
   - **Requires Authentication**: false
   - **Requires Approval**: false

2. **Search published recipes by intent, stack and constraints** 
   - **Action ID**: search-recipes  
   - **Operation ID**: search_recipes  
   - **Method**: POST 
   - **Relative Path**: /v1/catalog/search  
   - **Parameters**: 
     - **Body**: 
       - **Limit**: 5
       - **Query**: Host ai workflow runner with Spring Boot: worker execution and job state
   - **Requires Authentication**: false
   - **Requires Approval**: false

3. **Prepare a side-effect-free deployment plan for an authorized project** 
   - **Action ID**: plan:page:recipes:ai-workflow-runner:spring-boot:worker-state  
   - **Operation ID**: plan_deployment  
   - **Method**: POST  
   - **Relative Path**: /v1/catalog/plan 
   - **Parameters**:  
     - **Body**: 
       - **Inputs**: {}
       - **Project ID**: ""
       - **Recipe ID**: page:recipes:ai-workflow-runner:spring-boot:worker-state 
       - **Recipe Revision**: r1
   - **Requires Authentication**: true
   - **Requires Approval**: false

4. **Read the existing agent authentication setup** 
   - **Action ID**: auth-setup  
   - **Operation ID**: existing_auth_setup 
   - **Method**: GET 
   - **Relative Path**: /mcp/setup  
   - **Requires Authentication**: false
   - **Requires Approval**: false

5. **Browse AI workflow runner** 
   - **Action ID**: browse:workload:ai-workflow-runner  
   - **Operation ID**: browse_node  
   - **Method**: GET 
   - **Relative Path**: /v1/catalog/nodes/workload%3Aai-workflow-runner  
   - **Parameters**:  
     - **Node ID**: workload:ai-workflow-runner
   - **Requires Authentication**: false
   - **Requires Approval**: false

6. **Browse Spring Boot** 
   - **Action ID**: browse:stack:framework-spring-boot  
   - **Operation ID**: browse_node  
   - **Method**: GET 
   - **Relative Path**: /v1/catalog/nodes/stack%3Aframework-spring-boot  
   - **Parameters**:  
     - **Node ID**: stack:framework-spring-boot
   - **Requires Authentication**: false
   - **Requires Approval**: false

7. **Browse Dedicated worker process** 
   - **Action ID**: browse:pattern:dedicated-worker-process  
   - **Operation ID**: browse_node  
   - **Method**: GET 
   - **Relative Path**: /v1/catalog/nodes/pattern%3Adedicated-worker-process  
   - **Parameters**:  
     - **Node ID**: pattern:dedicated-worker-process
   - **Requires Authentication**: false
   - **Requires Approval**: false

8. **Browse Deploy AI app** 
   - **Action ID**: browse:intent:deploy-ai-app  
   - **Operation ID**: browse_node  
   - **Method**: GET 
   - **Relative Path**: /v1/catalog/nodes/intent%3Adeploy-ai-app  
   - **Parameters**:  
     - **Node ID**: intent:deploy-ai-app
   - **Requires Authentication**: false
   - **Requires Approval**: false