How adsblol/infra works
Main Components
a. External Components:
• User/Aircraft (data source)
• Public Internet Interface
b. Core Services:
• Ingest Service (readsb)
• MLAT Service (mlat-server)
• Hub Service (readsb)
• Planes Service (readsb with tar1090)
• Redis (for data storage)
• HAProxy (load balancer)
• API Service
• History Service
[External Layer]
• ↓
[Ingestion Layer]
• ↓
[Processing Layer]
• ↓
[Presentation Layer]
Key Relationships to Highlight
Primary Data Flow:
User → Ingest → Hub → Planes
Secondary Data Flow:
Ingest → MLAT → Hub → Planes
Specific Design Elements
• Rectangles: Kubernetes deployments
• Hexagons: External interfaces
• Rounded rectangles: Services
• Blue: Core services (Ingest, Hub, Planes)
• Green: MLAT-related components
• Yellow: Supporting services (Redis, HAProxy)
• Gray: External components
Implementation Details
a. Kubernetes Components:
• Namespace boundaries
• Service relationships
• Public-facing services
b. Network Policies:
• Allowed communication paths
• Security boundaries
Technical Specifications
Annotations for:
• Service types (readsb, mlat-server)
• Data formats (ADS-B data)
• Public endpoints
• Internal communication paths
┌─ Public Interface ─────────────┐
• (HAProxy, Ingress) │
• Data Ingestion ──────────────┤
• (Ingest Service) │
• Data Processing ─────────────┤
• (Hub, MLAT) │
• Data Presentation ───────────┤
• (Planes Service, API) │
• ┘