How anvayb/trackflow works
Project type and purpose
• TrackFlow is a full-stack, microservices-based logistics tracking platform.
• It provides order management, invoice generation, notifications, and integrates with AWS in production.
File structure
• Top-level files: Makefile (orchestrates local vs. prod), docker.compose.yml (local multi-container), GitHub workflows (CI/CD).
• Microservices folders:
• orders/ (Node.js service on port 3001)
• invoices/ (Node.js service on port 3003, writes PDFs to local exports or S3)
• notifications/ (Node.js service on port 4000, sends emails via SES)
• Frontend folder: React+TypeScript app built with Vite, communicates with services.
• No dedicated “shared” library—each service has its own package.json/node_modules.
README for additional insights
• Development: in-memory storage, local Docker Compose.
• Production: AWS DynamoDB (orders + customers), S3 (invoices), SES (emails).
• Entry points:
• orders: server.js exposes REST endpoints
• invoices: server.js endpoint to generate PDF by calling orders and persisting to S3 or local FS
• notifications: server.js sends transactional emails
Detailed but concise
• Local vs. cloud storage differences.
• Docker Compose network overlay for local.
• CI/CD pipelines as side note (GitHub Actions).