### Host client portal with Spring Boot: application activity history

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

#### Representative Queries
- Host client portal with Spring Boot: application activity history
- Where can I host Client portal built with Spring Boot?
- I need an application-owned event schema and tested history queries; not native platform audit logs.

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

#### Infrastructure Requirements
- **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **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.

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

#### 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 client portal itself (your domain records, validation rules and concurrency policy) is application code and was not separately tested; the pattern checks are what was verified.

#### Cost Estimate
- **Monthly Amount**: $10.00 USD
  - **App Server**: s-1vcpu-1gb - $5.00
  - **Managed PostgreSQL Database**: s-1vcpu-1gb - $5.00  
  > Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

#### Next Actions
- **[Browse the catalog index](https://api.ample.computer/v1/catalog)**: Search published recipes by intent, stack, and constraints.
- **[Prepare a side-effect-free deployment plan](https://api.ample.computer/v1/catalog/plan)** for an authorized project.