Host approval workflow with Spring Boot: relational workspace data · Ample Computer
Host Approval Workflow with Spring Boot: Relational Workspace Data
Deploy an approval workflow 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 approval workflow-specific behavior (your record schema, states and access rules) is your application code on that verified basis.
Verified: November 6, 2026
What It Runs On
Compute
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgres
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and noDATABASE_URLis 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, thenjava -jaron the jvm-21 template (Temurin JDK 21) withserver.portread fromPORT).A PostgreSQL driver reading
DATABASE_URLat 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 packageRuntime
javaSizes
-1vcpu-2gbStart
java -jar $(ls target/*.jar | grep -v -- '-plain' | head -n 1)Template
jvm-21
Steps
Build and Start.
./mvnw -q -DskipTests package(or the Gradle wrapper) producing one application jar, thenjava -jaron the jvm-21 template (Temurin JDK 21) withserver.portread fromPORT. The server must bind0.0.0.0onPORT.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.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> --publicVerify. Fetch the live URL and the pattern self-test route(s) (
/p/relational-records) from the example; then run your own checks. On failure readample logs <deployment_id> --kind buildthen--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
November 6, 2026 · canary run
Spring Boot pattern fixture deployed on Ample (./mvnw -q -DskipTests package(or the Gradle wrapper) producing one application jar, thenjava -jaron the jvm-21 template (Temurin JDK 21) withserver.portread fromPORT); 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).November 6, 2026 · canary run
The same Spring Boot app deployed with a--release-commandmigration; 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-2gbwith the example fixture. - The pattern checks verified the platform side; the approval workflow itself (your record schema, states and access rules) is your application code.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.