How boubeinstein/swim-ti-yp-prototype works
This repository configures a SWIM-TI demo platform: ADS-B traffic is retrieved from OpenSky, published through a broker, and consumed by an Explorer map; the Subscription Manager exposes REST operations for topics and subscriptions and stores their metadata. The tree primarily contains service configuration rather than application implementation, so the graph follows the README’s documented relationships and does not infer internal behavior from unsampled files.
Main entry points: subscription_manager Subscription Manager · swim_adsb SWIM ADS-B · swim_explorer SWIM Explorer · rabbitmq.conf RabbitMQ Broker
Components 9
Traffic Applications
- SWIM ADS-B
services/swim_adsb - SWIM Explorer
services/swim_explorer
Subscription Management
- Subscription Manager
services/subscription_manager - Initial Provisioning
services/subscription_manager/provision
Platform Services
- RabbitMQ Broker
services/broker/rabbitmq/rabbitmq.conf - PostgreSQL Metadata
services/db/postgres - Web Server
services/web_server/nginx/conf.d/nginx.conf
Other components
- OpenSky Network
- External Consumer
Connections 9
- OpenSky Network → SWIM ADS-B: provides traffic
README.md - SWIM ADS-B → Subscription Manager: publishes topics
README.md - SWIM ADS-B → RabbitMQ Broker: publishes traffic
README.md - External Consumer → Subscription Manager: manages subscriptions
README.md - Subscription Manager → RabbitMQ Broker: manages topics
README.md - Subscription Manager → PostgreSQL Metadata: stores metadata
README.md - SWIM Explorer → Subscription Manager: subscribes to topics
README.md - SWIM Explorer → RabbitMQ Broker: receives traffic
README.md - External Consumer → SWIM Explorer: views map
README.md