# Host event registration with Spring Boot: structured data imports

Deploy a event registration built with Spring Boot on Ample using the bulk import staging 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, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables. Verified on Spring Boot: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Not separately tested: your import format, mapping and conflict rules; treat the event registration-specific behavior as your application code.

## Summary

- **Family**: Workload recipe  
- **Release Status**: published  
- **Support Status**: verified  
- **Execution Status**: ready  
- **Docs Only**: false

## 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)
- A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables
- An Ample account token with servers:write, databases:read, buckets:read

## Resource Requirements

- **Compute**  
- **Postgres**  
- **S3-compatible object storage**

## 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 bulk import staging: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

3. **Wire object storage**  
   Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket.

4. **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 --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...`

5. **Verify**  
   Fetch the live URL and the pattern self-test route(s) (/p/bulk-import-staging) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.  
   Command: `ample logs  --kind build`

## Examples

- **Spring Boot pattern fixture**  
  Multi-pattern Spring Boot app whose bulk import staging module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
  Source reference: `tests/deploy-canaries/spring-boot-patterns`

## Success Checks

- App responds on its public URL  
- Bulk-import-staging self-test

## 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 event registration itself (your import format, mapping and conflict rules) is application code and was not separately tested; the pattern checks are what was verified.

## Evidence Summary

- **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 bulk-import-staging and configuration-secrets.