# Host product catalog with Spring Boot: relational catalog data

Deploy a product catalog built with Spring Boot on Ample using the transactional workflows 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: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Not separately tested: your domain records, validation rules and concurrency policy; treat the product catalog-specific behavior as your application code.

## Representative Queries
1. Host product catalog with Spring Boot: relational catalog data
2. Where can I host Product catalog built with Spring Boot?
3. I need catalog tables, transactional update logic and application-level access boundaries.

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

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

## Tested Configuration
- **Template**: jvm-21
- **Runtime**: java
- **Size**: s-1vcpu-2gb
- **Build**: ./mvnw -q -DskipTests package
- **Start**: java -jar $(ls target/*.jar | grep -v -- '-plain' | head -n 1)

## 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 transactional workflows: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). 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/transactional-workflows) 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
1. App responds on its public URL: **http_get** /, expect **ample canary spring boot patterns**.
2. Transactional-workflows self-test: **http_get** /p/transactional-workflows, expect **tx=ok history=2 conflict=rejected**.

## 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 product catalog itself (your domain records, validation rules and concurrency policy) 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.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Components**:
   1. App server - Size: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
   2. 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
1. **Canary Run**: Spring Boot pattern fixture deployed on Ample. Checks passed for transactional-workflows 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
2. **Canary Run**: The same Spring Boot app deployed with a --release-command migration; the marker it created was readable after activation.
   - Observed At: 2026-09-20T22:49:19Z
   - Implementation Revision: af6f45adea26-dirty (CLI af6f45a)
   - Expires At: 2027-03-19T22:49:19Z

## Next Actions
1. **Browse the catalog index**: GET /v1/catalog
2. **Search published recipes by intent, stack and constraints**: POST /v1/catalog/search; query: Host product catalog with Spring Boot: relational catalog data
3. **Prepare a side-effect-free deployment plan for an authorized project**: POST /v1/catalog/plan
4. **Read the existing agent authentication setup**: GET /mcp/setup
5. **Browse Product catalog**: GET /v1/catalog/nodes/workload%3Aproduct-catalog
6. **Browse Spring Boot**: GET /v1/catalog/nodes/stack%3Aframework-spring-boot
7. **Browse Transactional workflows**: GET /v1/catalog/nodes/pattern%3Atransactional-workflows
8. **Browse Deploy web app**: GET /v1/catalog/nodes/intent%3Adeploy-web-app

## Formats
- [HTML Format](/content/recipes/product-catalog/spring-boot/relational-catalog/index.html)
- [Markdown Format](/content/recipes/product-catalog/spring-boot/relational-catalog.md)
- [JSON Format](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aproduct-catalog%3Aspring-boot%3Arelational-catalog)