How audioboxer217/tkd_registration_backend works
Project Type and Purpose
This is a backend service component of a larger Taekwondo tournament registration system, implemented as a serverless application using AWS services. The project follows a event-driven, microservices-style architecture.
Main Components
a. Core Processing Services:
• Process Entries Service (Main handler)
• Badge Generation Service
• AWS-Google Drive Sync Service
b. Storage Systems:
• Amazon DynamoDB (Registration data)
• S3 Buckets (Multiple buckets for badges, config, profile pictures)
c. Message Queue:
• Amazon SQS (For asynchronous processing)
d. External Service Integrations:
• Stripe API (Payment processing)
• Google Drive API (File synchronization)
• Challonge API (Tournament management)
• Email Service (SMTP)
Top Layer: External Interfaces (APIs)
Middle Layer: Core Services
Bottom Layer: Storage & Infrastructure
Key Architectural Patterns to Highlight
a. Serverless Architecture:
• Lambda functions for each service
• API Gateway as entry point
b. Event-Driven Pattern:
• SQS queue connections
• Event flow between services
c. Data Flow:
• Entry processing flow
• Badge generation pipeline
• Sync operations
Implementation Details
a. Components:
┌─ API Gateway
• Lambda Functions
• Process Entries
• Generate Badges
• Sync AWS-GDrive
• Storage
• DynamoDB
• S3 Buckets
• External Services
• Stripe
• Google Drive
• Challonge
b. Important Configurations:
• Environment variables connections
• Security boundaries
• AWS resource relationships
Documentation Elements
• Version/environment indicators
• Deployment paths (Zappa)
• Configuration dependencies
Remember to include the local development setup path as an alternative flow, showing how the system can be tested and developed locally using the virtual environment and configuration files.