SMMUN website and registration system

🌐 smmun.com

Cloud-native, event-driven backend for handling conference registrations on Google Cloud Platform.

---

Architecture

Data Model

---

Overview

1. Users submit a form via a static frontend (Firebase Hosting)
2. The API (Cloud Run, FastAPI):
   • validates input
   • absorbs duplicate submits using an idempotency key
   • uploads files to Cloud Storage
   • stores the submission, idempotency record, and outbox job atomically in Firestore
   • returns confirmation once the submission is durably accepted
3. An outbox publisher (Cloud Run functions) asynchronously publishes pending submission events to Pub/Sub
   • one trigger reacts immediately to newly created outbox rows
   • a scheduled sweep revisits pending/stale rows until they are sent
4. A worker (Cloud Functions / Cloud Run functions) processes submissions asynchronously:
   • generates signed URLs
   • writes data to Google Sheets
   • sends confirmation emails (Resend)
5. Firestore tracks submission state:

   pending → processing → completed / failed
   

---

Stack

GCP

• Cloud Run
• Cloud Storage
• Firestore
• Pub/Sub
• Cloud Run functions

External

• Google Sheets API
• Resend API

---

Key points

• Event-driven architecture (Pub/Sub)
• Asynchronous processing via worker
• API-level idempotency for submission ingestion
• Reliable asynchronous delivery via Firestore outbox
• Secure file access with signed URLs
• Structured logging with request tracing
• Infrastructure managed with Terraform

---

Structure

• /api FastAPI service (Cloud Run)
• /worker Submission processor (Cloud Run functions)
• /outbox Outbox publisher and sweep handlers (Cloud Run functions)
• /front Svelte frontend
• /infra Terraform code
• /docs Architecture diagram

---

Author

Bruno Ancona - Software Engineering @ Universidad Anáhuac Mayab