How audioboxer217/tkd_registration_frontend works
Main Components
a. Client Layer:
• Web Browsers (Users and Admins)
• Static Assets (JS files in /static/js)
• HTML Templates (in /templates directory)
b. Frontend Application Layer:
• Flask Web Application (app.py)
• Form Processing Components
• Template Engine
• Authentication System (evident from login.html)
c. Backend Services Layer:
• Process Entries Service
• Badge Generation Service
• AWS-GDrive Sync Service
d. Data Storage Layer:
• DynamoDB Tables
• S3 Buckets (multiple buckets for different purposes)
e. Message Queue Layer:
• AWS SQS Queue
f. External Services:
• Stripe Payment Processing
• Google Drive API
• Challonge API
• Google Maps API (from environment variables)
┌─ Client Tier ─────────────────────────┐
• Web Browsers │ Static Assets │ Templates│
• ┴───────────────┴─────────┘
• ↓
┌─ Frontend Application Tier ───────────┐
• Flask App │ Forms │ Auth │ API Client │
• ┴───────┴──────┴───────────┘
• ↓
┌─ Backend Services Tier ──────────────┐
• Entry Processing │ Badges │ Sync │
• ┘
• ↓
┌─ Infrastructure Tier ───────────────┐
• DynamoDB │ S3 │ SQS │ Email Service │
• ┴────┴─────┴──────────────┘
Key Flows to Highlight
a. Registration Flow:
• User → Frontend → Form Processing → SQS → Entry Processing → DynamoDB
• Payment Processing: Frontend → Stripe API → Backend Confirmation
b. Admin Flow:
• Admin → Frontend → Backend Services → Data Storage
• Badge Generation Flow
• AWS-GDrive Sync Flow
Important Details
• Environment configurations (shown in /envs directory)
• Security boundaries
• API integration points
• Data flow directions
• Error handling paths (evident from registration_error.html)