# Host recruiting tracker with Spring Boot: relational workspace data

Deploy a recruiting tracker built with Spring Boot on Ample using the relational records 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 workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). The recruiting tracker-specific behavior (your record schema, states and access rules) is your application code on that verified basis.

supportverifiedreleasepublishedagent runready

VerifiedNovember 6, 2026

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)  
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)  
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

## You need

- 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

## Exact tested configuration

build./mvnw -q -DskipTests package

runtimejava

sizes-1vcpu-2gb

startjava -jar $(ls target/*.jar | grep -v -- '-plain' | head -n 1)

templatejvm-21

## 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.** The fixture's module implements relational records: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). 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 needs an answer first). Re-running with no change is a no-op.

```  
$ ample deploy . --name <app-name> --public  
```

4.  **Verify.** Fetch the live URL and the pattern self-test route(s) (/p/relational-records) from the example; then run your own checks. On failure read `ample logs <deployment_id> --kind build` then `--kind runtime`.

```  
$ ample logs <deployment_id> --kind build  
```

## How it was checked

✓app responds on its public URL· http get/ → “ample canary spring boot patterns”

✓relational-records self-test· http get/p/relational-records → “records=ok transitions=true isolation=true”

## Evidence

1. November 6, 2026 · canary run  
Spring Boot pattern fixture deployed on Ample (./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); checks passed for relational-records and configuration-secrets. Pattern proof: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).

2. November 6, 2026 · canary run  
The same Spring Boot app deployed with a --release-command migration; the marker it created was readable after activation.

## Tested examples

- **Spring Boot pattern fixture.** Multi-pattern Spring Boot app whose relational records module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

## What it doesn’t cover

- Verified on the jvm-21 template at s-1vcpu-2gb with the example fixture.

- The pattern checks verified the platform side; the recruiting tracker itself (your record schema, states and access rules) is your application code.

- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.
