PROJECT NOTES / CLOUD & APPLICATIONS
Cloud Coordination Hub
Bring the plan together.
A shared workspace for event registrations, automatic waitlists, polls, and appointments, with an AWS architecture prepared for future deployment.
- React
- TypeScript
- Express
- AWS / DynamoDB
- SQLite
- Docker
- GitHub Actions
Source repository is private.
THE CONTEXT
A closer look.
The problem
Coordinating events across separate forms and spreadsheets makes capacity, participation, and scheduling hard to keep consistent. A shared application needs to prevent duplicate registrations and conflicting bookings.
What I built
As part of a university team project, I worked on a React and TypeScript workspace backed by a Node.js and Express API. The functional local prototype supports event registration, FIFO waitlists, polls, and appointment reservations, with persistent SQLite storage and a separate DynamoDB adapter.
HOW IT FITS TOGETHER
The architecture.
- 01
React, Vite, and Tailwind CSS provide the responsive interface.
- 02
An Express API validates requests and enforces authentication and resource ownership.
- 03
SQLite persists local records; the DynamoDB adapter uses conditional transactions for shared storage.
- 04
CloudFormation prepares an AWS load balancer, private EC2 application instances, and DynamoDB access. This cloud architecture is not deployed.
ENGINEERING DETAILS
Decisions that matter.
Consistent participation
Version-checked transactions protect capacity and duplicate registrations. Cancelling a confirmed place promotes the next person in the FIFO waitlist in the same transaction.
One workspace, clear boundaries
Server-side ownership checks protect organizer resources. Polls accept one vote per authenticated person, and appointment slots permit one booking at a time.
A measured path to cloud
GitHub Actions validates the application and prepares build artifacts. Docker and CloudFormation support future deployment; no live AWS deployment or public demo is claimed.
Verified against authorized project documentation and implementation. Source remains private. The illustration shows the local application and a separately prepared cloud storage path.
UP NEXTMeowVerse · Mobile Game