Host AI Chat Application with Spring Boot: Postgres-backed State

Summary

Deploy an AI chat application 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 chat application-specific behavior as your application code.

Representative Queries

• Host ai chat application with Spring Boot: Postgres-backed state
• Where can I host AI chat application built with Spring Boot?
• I need a durable state schema and retry/recovery semantics implemented by application code.

Resource Requirements

• Compute: primitive:compute
• Postgres: primitive:postgres

Infrastructure Requirements

1. Compute: 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: 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.

Tested Configuration

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

Workflow Steps

1. 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.
2. Implement the Pattern on PostgreSQL: Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. Deploy: 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. Command: ample deploy . --name --public
4. Verify: 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 build then --kind runtime. Command: ample logs --kind build

Examples

• Spring Boot Pattern Fixture: Multi-pattern Spring Boot app whose durable job state module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success Checks

1. App responds on its public URL. Kind: http_get, Path: /, Expect: ample canary spring boot patterns.
2. Durable-job-state self-test. Kind: http_get, Path: /p/durable-job-state, Expect: job=done attempts=1 idempotent=true.

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 chat application itself was not separately tested; the pattern checks are what was verified.

Cost Estimate

• Monthly Amount: $10.00 (currency: USD)
• 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)
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Evidence Summary

1. Canary Run: Spring Boot pattern fixture deployed on Ample with checks passed for durable-job-state and configuration-secrets.

• Observed At: 2026-09-21T02:34:39Z
• Implementation Revision: 1d28ae0-dirty (CLI 0.1.21)
• Expires At: 2027-03-20T02:34:39Z

2. Canary Run: The same Spring Boot app deployed with a --release-command migration; the marker it created was readable after activation.

• Observed At: 2026-09-20T22:49:19Z
• Implementation Revision: af6f45adea26-dirty (CLI af6f45a)
• Expires At: 2027-03-19T22:49:19Z

Next Actions

• Browse the catalog index: Browse the catalog index.
• Search published recipes: Search published recipes by intent, stack and constraints.
• Prepare a deployment plan: Prepare a side-effect-free deployment plan for an authorized project.
• Read existing authentication setup: Read the existing agent authentication setup.
• Browse AI chat application: Browse AI chat application.
• Browse Spring Boot: Browse Spring Boot.
• Browse Durable job state: Browse Durable job state.
• Browse Deploy AI app: Browse Deploy AI app.