mirror of
https://github.com/gadgethd/ukmesh.git
synced 2026-09-11 09:35:35 +00:00
Ben
21224a0525
- split backend API into route/service/repository boundaries across stats, owner, and pathing\n- extract shared API bootstrap and helper modules\n- reduce MapLibreMap into smaller frontend map modules with extracted builders, config, popup UI, and types\n- continue worker modularization by extracting RF terrain/tile helpers alongside RF config and loss helpers\n- add repo-local architecture, DB lifecycle, link model, pathing, frontend map, and contributing docs\n\nThis is the verified refactor checkpoint: backend and frontend builds passed, worker syntax checks passed, affected containers were rebuilt, and /healthz is OK.
2.6 KiB
2.6 KiB
Architecture
meshcore-analytics is split across three main runtimes:
backend- HTTP API
- WebSocket live stream
- DB access
- owner dashboard/session logic
- path resolver orchestration
frontend- map rendering
- packet feed
- owner/stats pages
- external stores for live state
viewshed-worker- coverage generation
- physical link evaluation
- radio-neighbour ingestion support
- RF/path-loss calculations
Backend domain layout
backend/src/api/- thin HTTP route modules and bootstrap wiring
backend/src/platform/- runtime configuration
backend/src/db/- pool setup, base schema, migrations
backend/src/stats/- stats service/repository logic
backend/src/owner/- owner auth/session/live service and repository logic
backend/src/pathing/- pathing service/repository orchestration
backend/src/path-beta/- resolver implementation and worker pool
backend/src/api/utils/- route-scoped shared helpers
backend/src/api/bootstrap/- cache and limiter construction
Frontend domain layout
frontend/src/components/Map/MapLibreMap.tsx- imperative map orchestration only
frontend/src/components/Map/geojsonBuilders.ts- pure builders for node/link/coverage/clash GeoJSON
frontend/src/components/Map/mapConfig.ts- map constants and style config
frontend/src/components/Map/NodePopupContent.tsx- popup rendering
frontend/src/store/overlayStore.ts- path overlay UI state
frontend/src/hooks/useNodes.ts- live node/packet store
frontend/src/hooks/useCoverage.ts- coverage store
frontend/src/hooks/useLinkState.ts- link store
Worker domain layout
viewshed-worker/worker.py- queue orchestration and DB write flow
viewshed-worker/rf/config.py- RF thresholds and calibration state
viewshed-worker/rf/loss.py- path-loss calculation helpers
viewshed-worker/rf/terrain.py- tile download, terrain sampling, VRT helpers
Data flow
- MQTT packets arrive in the backend ingest path.
- Backend normalizes packet/node updates and publishes live messages.
- Frontend stores ingest live node/packet/link updates without routing them through
Appstate. - Coverage and physical links are computed asynchronously by the worker.
- Pathing combines physical links, multibyte evidence, and cached history to produce purple/red paths.
Operational rules
- app startup must not run heavy historical backfills
- route modules should stay thin
- repositories own SQL
- services own orchestration and shaping
- worker RF math should stay isolated from queue orchestration