# Sports clubs: event registration using Next.js

An event registration blueprint for sports clubs built with Next.js on Ample. Domain schema:

- **course_groups** (team_or_class, season, age_group): teams and classes;
- **memberships** (course_group_id, member_reference, guardian_reference, role): players, guardians, and coaches;
- **sessions** (course_group_id, starts_at, venue, type): training and fixtures;
- **materials** (course_group_id, title, object_key, visibility): schedules and coaching resources;
- **events** (seq, record_type, record_id, kind, at): application-owned history written in the same transaction.

Public information: teams, seasons and fixtures, venues, membership fees. Kept out of scope until handling is reviewed: minor members and medical notes, safeguarding records. Medical and safeguarding records are sensitive; only schedules and coaching materials are modeled. Technical basis verified on Next.js: 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).

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

- [S3-compatible object storageverified](/content/discover/primitive/s3-compatible-object-storage/index.html)  
  Buckets speak the S3 API with SigV4 credentials Ample Computer issues; `ample bucket upload-url` returns a presigned upload URL. PutObject and GetObject are checked by canary.

## You need

- A Next.js project (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template)
- A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
- Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables
- A review of which sports clubs data classes may be handled at all; this blueprint models public information only

## Exact tested configuration

- **build**: `npm run build --if-present`
- **install**: `npm install`
- **runtime**: `node`
- **sizes**: 1vcpu-1gb
- **start**: `npm run start`
- **template**: node-22

## Steps

1. **Model the sports clubs domain.** Create the tables course_groups, memberships, sessions, materials, events. Teams and classes live in course_groups; keep the sensitive classes (minor members and medical notes, safeguarding records) out of this schema.

2. **Workflow step 1.** Model sessions with capacity and registrations with status.

3. **Workflow step 2.** Register transactionally with a capacity check and an event per registration.

4. **Workflow step 3.** Reject stale concurrent updates.

5. **Workflow step 4.** Deploy and verify history and conflict handling.

6. **Deploy.** Run the synchronous deploy once and read the result. Re-running with no change is a no-op.

```
   $ ample deploy . --name <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
   ```

7. **Verify.** Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the sports clubs workflow.

```
   $ ample logs <deployment_id> --kind build
   ```

## How it was checked

- ✓ app responds on its public URL  
  `http get/` → “ample canary next js patterns”

- ✓ transactional-workflows self-test from the example  
  `http get/p/transactional-workflows` → “see the pattern fixture checks”

## Evidence

- November 5, 2026 · canary run  
  Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template); the transactional workflows checks passed: 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 blueprint's Sports clubs schema and workflow below build on that verified basis.

## Tested examples

- **Next.js pattern fixture.** Verified transactional workflows basis for this blueprint.

## What it doesn’t cover

- The technical basis (transactional workflows on Next.js) was verified with the pattern fixture; the sports clubs schema and workflow are an original design for this blueprint, built on that basis.
- Medical and safeguarding records are sensitive; only schedules and coaching materials are modeled.
- Verified on the node-22 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); `ample bucket upload-url` returns presigned upload URLs.
