### Host crm with Spring Boot: relational workspace data

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

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

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

#### Infrastructure Requirements
1. **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.

2. **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.

#### 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  --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 s-1vcpu-2gb with the example fixture; other sizes, templates and Spring Boot major versions are not verified.
- The crm 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
- **Authority:** true
- **Basis:** size prices from pricing.toml (loaded by the API)
- **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.