How shizlie/hcproduct-switchboard-mockup works
Main Components
a) Client Layer:
• Website (Static HTML files)
• Connection to API endpoints
b) API Gateway Layer:
• AWS API Gateway (implied from Lambda usage)
• Custom domain (switchboard.harrycorn.com)
c) Compute Layer:
• AWS Lambda Functions
• Caching mechanism using Ephemeral Storage (/tmp)
• Reserved Concurrency settings (10 instances)
d) Data Processing Layer:
• Query Processing Service
• Data Processing Service
• Logging Service
e) Database Layer:
• Supabase (as indicated by config files)
[Client Layer]
• ↓
[API Gateway]
• ↓
[Lambda Function]
• ↙ ↘
[Cache] [Processing Services]
• ↓
[Database]
Important Details to Highlight
a) Lambda Configuration:
• 10GB Ephemeral Storage allocation
• Reserved Concurrency (10 instances)
• Cold start (7s) vs. warm start (1.2s-2s) times
b) Service Integration:
• Relationship between API management and API usage routes
• Data flow through processing services
Additional Elements
• A metrics/logging flow showing how usage patterns are collected
• Caching mechanism's interaction with the main processing flow
• Where future Evidence.dev integration might fit for log analysis
Technical Notes
• Node.js runtime environment
• Supabase integration points
• API endpoint routing structure
• Cache invalidation flow