How lf-connectivity/isptoolbox works
Project Type & Purpose
• This is a full-stack, containerized web application (“ISP Toolbox”) that provides mapping and analytics tools (market evaluator, LOS-check, DSM export, network cost comparison).
• Backend: Django + Django REST Framework + Channels (websockets) + Celery for async tasks.
• Frontend: TypeScript/React-style SPA served from a static container.
• Infrastructure as Code: Terraform. Deployment: Docker/ECS on AWS (ALB, EC2, ECR, ECS), RDS (Postgres), ElastiCache (Redis), S3 for static assets. Lambdas at CloudFront Edge for custom request/response logic.
Architectural Patterns & Principles
• Layered separation:
• Presentation (browser, static container)
• API/Websocket (Django)
• Business logic (Celery tasks)
• Data (Postgres, Redis, S3)
• Message-driven async: Celery + Redis decouples long-running tasks.
• Infrastructure as code: Terraform modules for network, autoscaling, IAM, load-balancer.
• Container orchestration: ECS services, Docker Compose for local dev.
• Blue: External/client
• Green: Edge/Ingress
• Yellow: Compute services (Django, Node, Celery)
• Orange: Data stores (Postgres, Redis, S3)
• Gray: IaC/CI (Terraform, GitHub Actions)
Essential Details to Capture
• Reverse proxy (Nginx) sits in front of all services.
• WebSocket traffic handled by Django Channels, backed by Redis.
• Celery broker = Redis; results may live in Postgres or S3.
• Node-webserver handles map-specific middleware.
• Lambda@Edge functions apply custom logic at CloudFront.
• Terraform modules define autoscaling, networking, secrets, IAM.
• GitHub workflows build & push Docker images to ECR, then ECS deploy.