# Host help desk with Spring Boot: relational workspace data

Deploy a help desk 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 help desk-specific behavior as your application code.

## Representative Queries
- Host help desk with Spring Boot: relational workspace data
- Where can I host Help desk built with Spring Boot?
- I need a workspace-specific schema, state transitions and access rules.

## Resource Requirements
- primitive:compute
- primitive:postgres

## Infrastructure Requirements
### Compute
- **Id**: primitive:compute
- **Status**: verified
- **Summary**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

### Postgres
- **Id**: primitive:postgres
- **Status**: verified
- **Summary**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

## Framework
- Spring Boot

## Workload
- Help desk

## 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
### 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.

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

### 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`

## 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 Reference**: tests/deploy-canaries/spring-boot-patterns

## Success Checks
- **HTTP Get**: app responds on its public URL (expect: ample canary spring boot patterns)
- **HTTP Get**: relational-records self-test (expect: records=ok transitions=true isolation=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 help desk 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.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- **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.

## Evidence Summary
### Canary Run
- **Summary**: 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).
- **Observed At**: 2026-09-21T02:34:39Z

### Next Actions
- **Action**: Browse the catalog index
- **Operation**: GET /v1/catalog
- **Action**: Search published recipes by intent, stack and constraints
- **Operation**: POST /v1/catalog/search
- **Action**: Prepare a side-effect-free deployment plan for an authorized project
- **Operation**: POST /v1/catalog/plan
- **Action**: Read the existing agent authentication setup
- **Operation**: GET /mcp/setup
- **Action**: Browse Help desk
- **Operation**: GET /v1/catalog/nodes/workload%3Ahelp-desk
- **Action**: Browse Spring Boot
- **Operation**: GET /v1/catalog/nodes/stack%3Aframework-spring-boot
- **Action**: Browse Relational records
- **Operation**: GET /v1/catalog/nodes/pattern%3Arelational-records
- **Action**: Browse Deploy web app
- **Operation**: GET /v1/catalog/nodes/intent%3Adeploy-web-app