Dev: create an architecture diagram

vicb commented 5 months ago

List all the apps (server and front) and all the techno (Redis, Datastore, app engine, ...)

Fabian1535 commented 4 months ago

I'll like to help with this.

vicb commented 4 months ago

Components:

GCP Datastore (Track, Accounts)
Redis (GPS Positions and status)
Message Queue (triggers cloud run to post process the track, adding elevation and airspaces)
GCP Cloud functions (see above)
The server (API + static files)
The frontend (maps)
The airspace processing
GCP Storage (airspaces)

Apps:

airspaces: Scripts to decode airspaces files (different format) and write the output to GCP Storage
fetcher: VM that fetches the GPS positions from all the platform and push them to a REDIS in-memory DB
fxc-front: Frontend. Uses static files & API from the server. Load kml tiles from the GCP storage. Upload track to the Datastore via the server.
fxc-server: GCP App Engine node server. Serve static files, tracks, live tracks and API. Tracks are retrieve from the GCP Datastore. Live track are retrieved from the REDIS DB.

That should be enough to start something.

Ideally we can find some website that generate a diagream from a DSL, it would be easier to review/modify. A quick googling returned this article

Let me know if you have any questions! Thanks

vicb / flyXC