# Host Recruiting Tracker with Spring Boot: Relational Workspace Data

## Summary
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). Not separately tested: your record schema, states and access rules; treat the recruiting tracker-specific behavior as your application code.

## Framework
Spring Boot

## Workload
Recruiting tracker

## Release Status
Published

## Support Status
Verified

## Execution Status
Ready

## 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
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 blocked). Re-running with no change is a no-op.  
   Command: `ample deploy . --name <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 --kind build` then `--kind runtime`.  
   Command: `ample logs --kind build`

## Success Checks
- **App responds on its public URL**  
  Kind: `http_get`, Path: `/`, Expect: `ample canary spring boot patterns`
- **Relational-records self-test**  
  Kind: `http_get`, Path: `/p/relational-records`, Expect: `records=ok, transitions=true, isolation=true`

## Limitations
- Verified on the jvm-21 template at size `s-1vcpu-2gb` with the example fixture; other sizes, templates and Spring Boot major versions are not verified.
- The recruiting tracker itself (your record schema, states and access rules) is application code and was not separately tested; the pattern checks are what was verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

## Examples
- **Spring Boot pattern fixture**  
  Description: Multi-pattern Spring Boot app whose relational records module was checked live; the module is under `tests/deploy-canaries/_pattern-modules`.
  Source Ref: `tests/deploy-canaries/spring-boot-patterns`

## Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 10.0  
- **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. Buckets are allocation-priced per quota and not included.

## Last Verified At
2026-09-21T02:34:39Z

## Evidence Summary
- **Kind**: `canary_run`  
  Summary: Spring Boot pattern fixture deployed on Ample; checks passed for relational-records 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
  Scope: `{checks: ["/p/relational-records"], pattern: "pattern:relational-records", template: "jvm-21"}`

## Formats
- **HTML**: [Host recruiting tracker with Spring Boot: relational workspace data](/content/recipes/recruiting-tracker/spring-boot/relational-workspace/index.html)
- **Markdown**: [Host recruiting tracker with Spring Boot: relational workspace data (markdown)](/content/recipes/recruiting-tracker/spring-boot/relational-workspace.md)
- **JSON**: [Host recruiting tracker with Spring Boot: relational workspace data (json)](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Arecruiting-tracker%3Aspring-boot%3Arelational-workspace)