# Host Subscription Content with Spring Boot: Relational Catalog Data

Deploy a subscription content 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). The subscription content-specific behavior (your domain records, validation rules and concurrency policy) is your application code on that verified basis.

---

**Verified:** November 6, 2026

## What It Runs On

- [Computeverified](/content/discover/primitive/compute/index.html)
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)
  Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

## You Need

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

## Exact Tested Configuration

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

## 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 needs an answer first). Re-running with no change is a no-op.
   
   ```
   $ ample deploy . --name <app-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 <deployment_id> --kind build` then `--kind runtime`.
   
   ```
   $ ample logs <deployment_id> --kind build
   ```

## How It Was Checked

- ✓ app responds on its public URL · `http get/` → “ample canary spring boot patterns”
- ✓ transactional-workflows self-test · `http get/p/transactional-workflows` → “tx=ok history=2 conflict=rejected”

## Evidence

1. November 6, 2026 · canary run  
   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 transactional-workflows and configuration-secrets. Pattern proof: 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).

2. November 6, 2026 · canary run  
   The same Spring Boot app deployed with a `--release-command` migration; the marker it created was readable after activation.

## Tested Examples

- **Spring Boot pattern fixture.** Multi-pattern Spring Boot app whose transactional workflows module was checked live; the module is under `tests/deploy-canaries/_pattern-modules`.

## What It Doesn’t Cover

- Verified on the jvm-21 template at s-1vcpu-2gb with the example fixture.
- The pattern checks verified the platform side; the subscription content itself (your domain records, validation rules and concurrency policy) is your application code.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.
