How metecan/wape works
Main Components
A. Services Layer:
• API Service (Port 8000)
• Parser Service (Port 8001)
• Beanstalkd Queue Service
• PostgreSQL Database
• Supabase Storage (S3 Bucket)
Specific Component Details
• API Service |
• File Upload Handler |
• Queue Producer |
• S3 Upload Helper |
• Parser Service |
• Queue Consumer |
• File Parser |
• DB Insert Helper |
Flow Directions
→ Client to API: HTTP POST /page (file upload)
→ API to S3: File storage
→ API to Queue: File metadata
→ Queue to Parser: Processing tasks
→ Parser to DB: Parsed data storage
Important Notes
a) Environment Considerations:
• Docker container boundaries
• Port mappings (8000, 8001)
• Environment variables connection points
b) Technical Stack Callouts:
• Gofiber framework
• Beanstalkd queue
• Supabase Storage
• PostgreSQL database
Parsed data stored → PostgreSQL
Remember to indicate:
• Docker container boundaries
• Network connections between services
• External service dependencies
• Data flow directions
• API endpoints
• Queue channels
This system design should effectively communicate both the high-level architecture and the specific implementation details of the WAPE microservice system.