# Host Rest API with Spring Boot: Postgres-backed State

Deploy a REST API 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). The REST API-specific behavior (your job types, payload schema and retry policy) is your application code on that verified basis.

### 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`
- runtime: `java`
- sizes: `-1vcpu-2gb`
- start: `java -jar $(ls target/*.jar | grep -v -- '-plain' | head -n 1)`
- template: `jvm-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 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`.

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/durable-job-state`) 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”  
✓ durable-job-state self-test · http get `/p/durable-job-state` → “job=done attempts=1 idempotent=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 durable-job-state and configuration-secrets. Pattern proof: 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).

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 durable job state 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 REST API itself (your job types, payload schema and retry policy) is your application code.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.
