How rohanbhowmik2022/multi-cloud-dashboard works
This is a multi-cloud cost and service-status dashboard. Users choose AWS, Azure, or GCP, then view regional/availability-zone server counts and monthly service costs; a polling worker collects or generates those metrics, stores them, and the API serves them to the provider-specific pages. The README also documents Terraform infrastructure automation, represented as a separate capability rather than a runtime data-flow stage. Collection details vary by provider: sampled code shows AWS collection and dummy Azure/GCP metrics. Deployment pipelines are omitted.
Main entry points: App.js App routing · metrics.py Cost/status endpoints · worker.py Polling worker · main.tf Terraform provisioning
Components 19
Dashboard UI
- App routing
app/frontend/src/App.js - Cloud selector
app/frontend/src/components/CloudSelector.js - Dashboard header
app/frontend/src/components/Header.js - AWS dashboard
app/frontend/src/pages/AWS.js - Azure dashboard
app/frontend/src/pages/Azure.js - GCP dashboard
app/frontend/src/pages/GCP.js
Metrics API
- API server entry
app/backend/main.py - Cost/status endpoints
app/backend/api/metrics.py - API DB access
app/backend/core/database.py
Metric Collection
- Polling worker
app/worker/worker.py - AWS metrics
app/worker/aws_module.py - Azure metrics
app/worker/azure_module.py - GCP metrics
app/worker/gcp_module.py
Infrastructure
- Terraform provisioning
infra/terraform/main.tf - RDS database
infra/terraform/modules/database/main.tf - VPC and ALB
infra/terraform/modules/vpc/main.tf
Other components
- Dashboard user
- Metrics database
app/database/schema.sql - Cloud accounts
Connections 19
- Dashboard user → App routing: opens dashboard
README.md - App routing → Dashboard header: renders
app/frontend/src/App.js - App routing → Cloud selector: renders
app/frontend/src/App.js - App routing → AWS dashboard: selects page
app/frontend/src/App.js - App routing → Azure dashboard: selects page
app/frontend/src/App.js - App routing → GCP dashboard: selects page
app/frontend/src/App.js - API server entry → Cost/status endpoints: starts
app/backend/main.py - AWS dashboard → Cost/status endpoints: fetches AWS metrics
app/frontend/src/pages/AWS.js - Azure dashboard → Cost/status endpoints: fetches Azure metrics
app/frontend/src/pages/Azure.js - GCP dashboard → Cost/status endpoints: fetches GCP metrics
app/frontend/src/pages/GCP.js - Cost/status endpoints → API DB access: opens connection
app/backend/api/metrics.py - API DB access → Metrics database: queries
- Polling worker → AWS metrics: invokes collection
app/worker/worker.py - Polling worker → Azure metrics: invokes collection
app/worker/worker.py - Polling worker → GCP metrics: invokes collection
app/worker/worker.py - AWS metrics → Cloud accounts: collects metrics
- Polling worker → Metrics database: writes metrics
app/worker/worker.py - Terraform provisioning → RDS database: provisions
- Terraform provisioning → VPC and ALB: provisions