page:recipes:ai workflow runner:spring boot:persistent state
Host ai workflow runner with Spring Boot: Postgres-backed state
Summary
Deploy a AI workflow runner built with Spring Boot on Ample using the durable job state pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL. Verified on Spring Boot: a jobs table with a state and attempts counter, processing inside a row-locked transaction, and a second run that is a no-op (job=done attempts=1 idempotent=true). Not separately tested: your job types, payload schema and retry policy; treat the ai workflow runner-specific behavior as your application code.
Representative Queries
- Host ai workflow runner with Spring Boot: Postgres-backed state
- Where can I host AI workflow runner built with Spring Boot?
- I need a durable state schema and retry/recovery semantics implemented by application code.
Resource Requirements
- Compute
- Postgres
Infrastructure Requirements
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.
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.
Prerequisites
- A Spring Boot project that builds and starts 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).
- A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
- An Ample account token with servers:write, databases:read.
Workflow Steps
Build and start
./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 server must bind 0.0.0.0 on PORT.
Implement the pattern on PostgreSQL
- The fixture's module implements durable job state: a jobs table with a state and attempts counter, processing inside a row-locked transaction, and a second run that is a no-op (job=done attempts=1 idempotent=true). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
Deploy
ample deploy . --name --public- Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op.
Verify
ample logs --kind build- Fetch the live URL and the pattern self-test route(s) (/p/durable-job-state) from the example; then run your own checks. On failure read
ample logs --kind buildthen--kind runtime.
Success Checks
- App responds on its public URL
- Expect:
ample canary spring boot patterns
- Expect:
- Durable-job-state self-test
- Path:
/p/durable-job-state - Expect:
job=done attempts=1 idempotent=true
- Path:
Limitations
- Verified on the jvm-21 template at s-1vcpu-2gb with the example fixture; other sizes, templates, and Spring Boot major versions are not verified.
- The ai workflow runner itself (your job types, payload schema, and retry policy) is application code and was not separately tested; the pattern checks are what was verified.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
Cost Estimate
- Currency: USD
- Monthly Amount: 10.0
- Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.
Components
- App Server:
- Size: s-1vcpu-1gb
- Quantity: 1.0
- Monthly Amount: 5.0
- Managed PostgreSQL Database:
- Size: s-1vcpu-1gb
- Quantity: 1.0
- Monthly Amount: 5.0