# Host inventory manager with Quarkus: relational workspace data

Deploy an inventory manager built with Quarkus 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 Quarkus: 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 inventory manager-specific behavior as your application code.

## Representative Queries
- Host inventory manager with Quarkus: relational workspace data
- Where can I host Inventory manager built with Quarkus?
- I need a workspace-specific schema, state transitions and access rules.

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

## Infrastructure Requirements
### Compute
- **Label**: 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
- **Label**: 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 Quarkus project that builds and starts with the documented commands (./mvnw -q -DskipTests package producing one uber-jar (quarkus.package.jar.type=uber-jar), then java -jar on the jvm-21 template (Temurin JDK 21) with quarkus.http.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
- Command: `./mvnw -q -DskipTests package producing one uber-jar (quarkus.package.jar.type=uber-jar), then java -jar on the jvm-21 template (Temurin JDK 21) with quarkus.http.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`

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

## Success Checks
- **Description**: app responds on its public URL  
- **Kind**: http_get  
- **Path**: /  
- **Expect**: ample canary quarkus patterns

- **Description**: 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 Quarkus major versions are not verified.
- The inventory manager 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**:
    - **Name**: app server  
        - **Size**: s-1vcpu-1gb
        - **Quantity**: 1.0  
        - **Monthly Amount**: 5.0  
    - **Name**: 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**: Quarkus pattern fixture deployed on Ample (./mvnw -q -DskipTests package producing one uber-jar (quarkus.package.jar.type=uber-jar), then java -jar on the jvm-21 template (Temurin JDK 21) with quarkus.http.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-21T00:35:31Z
- **Implementation Revision**: c6c81daa9272c95c5ce381005ba7347a341e578f-dirty (CLI 0.1.21)
- **Expires At**: 2027-03-20T00:35:31Z

### Last Verified
- **At**: 2026-09-21T00:35:31Z

## Unknowns
- Region availability is unknown until a verified region fact is recorded.
- Compliance attestations are unknown; none are claimed.

## Formats
- **HTML**: [View here](/content/recipes/inventory-manager/quarkus/relational-workspace/index.html)
- **Markdown**: [View here](/content/recipes/inventory-manager/quarkus/relational-workspace.md)
- **JSON**: [View here](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Ainventory-manager%3Aquarkus%3Arelational-workspace)

## Next Actions
- **Browse Catalog**: [Browse the catalog index](#)
- **Search Recipes**: [Search published recipes](#)  
- **Prepare Deployment Plan**: [Prepare a side-effect-free deployment plan](#)
- **Read Existing Auth Setup**: [Read the existing agent authentication setup](#)
- **Browse Inventory Manager**: [Browse Inventory manager](#)
- **Browse Quarkus**: [Browse Quarkus](#)
- **Browse Relational Records**: [Browse Relational records](#)
- **Browse Deploy Web App**: [Browse Deploy web app](#)