Ready-to-Deploy Components

Reference implementations for DNOTAM and ED-254 services, built on top of the extensible framework. All projects are BSD 3-Clause licensed and open for contribution.

Core

Production modules for SWIM service integration

swim-dnotam-provider

Become a DNOTAM provider yourself. Receives events from internal Kafka topics, manages external subscriptions, and distributes via AMQP to consumers. Use when your organization is the authoritative source of aeronautical data.

  • Full Subscription Manager API
  • WFS GetFeature endpoint (OGC)
  • Dynamic queue provisioning per subscriber
  • OIDC/JWT authentication (any OpenID Connect provider)
Quarkus PostgreSQL Artemis Keycloak
View Repository

swim-dnotam-consumer

Production module for organizations that need to receive DNOTAM events. Connects to any AISP/EAD, manages subscriptions automatically, validates messages, and distributes to internal systems via Kafka.

  • Auto-subscription from config
  • Inbox/Outbox patterns (zero message loss)
  • XSD + business rules (pluggable)
  • GraphQL + REST APIs for queries
Quarkus MongoDB Kafka GraphQL
View Repository

swim-ed254-provider

ED-254 Arrival Sequence provider implementation. Publishes arrival sequence data to external consumers via AMQP. Same framework as DNOTAM, different service implementation.

  • Full Subscription Manager API
  • FIXM-based data model
  • Dynamic queue provisioning per subscriber
  • OIDC/JWT authentication
Quarkus PostgreSQL Artemis FIXM
View Repository

swim-ed254-consumer

ED-254 Arrival Sequence consumer implementation. Receives arrival sequence data from external providers and distributes to internal systems via Kafka.

  • Auto-subscription from config
  • Inbox/Outbox patterns (zero message loss)
  • FIXM validation
  • GraphQL + REST APIs for queries
Quarkus MongoDB Kafka GraphQL
View Repository

Validation & Testing

Tools for development, testing, and validation workflows

swim-dnotam-consumer-validator

Simulates an AISP (Aeronautical Information Service Provider) for testing and validating your Consumer implementation. Ultra-lightweight container that requires minimal resources. Optional component used during development and validation phases.

  • Full Subscription Manager API (SWIM Registry)
  • Integrated Artemis AMQP broker
  • 82 sample AIXM events included
  • Interactive scenario simulator
Quarkus Artemis AIXM 5.1.1 mTLS
View Repository

swim-dnotam-provider-validator

Conformance testing tool for SWIM providers. Provides a user interface for subscription management, real-time event visualization, and contract testing against provider implementations.

  • Subscription CRUD operations
  • Real-time event streaming
  • mTLS proxy support
  • Load testing capabilities
Quarkus HTMX SSE REST Client
View Repository

Try It

Deploy the complete platform locally and explore

swim-deploy-minikube

Helm charts and Ansible playbook for deploying the complete SWIM DNOTAM platform on Minikube. One command deploys Consumer Validator, Consumer, Provider, Provider Validator, Keycloak, Kafka, and all dependencies. Ready in ~7 minutes.

  • Single ansible-playbook command
  • All components pre-configured
  • mTLS certificates auto-generated
  • Works on Linux, macOS, Windows (WSL2)
Minikube Helm Ansible cert-manager
View Repository

Technologies Used

All components were developed and tested using enterprise-grade downstream versions. The upstream (community) versions are fully compatible and can be used without vendor dependency.

Category Upstream (Community) Downstream (Enterprise)
Application Framework Quarkus Red Hat Build of Quarkus
Message Broker (AMQP) Apache ActiveMQ Artemis Red Hat AMQ Broker
Event Streaming Apache Kafka Red Hat AMQ Streams
Identity & Access Keycloak Red Hat Build of Keycloak
Document Database MongoDB MongoDB (UBI Container)
Relational Database PostgreSQL PostgreSQL (UBI Container)
Certificate Management cert-manager cert-manager Operator for Red Hat OpenShift
Operator Development Operator SDK Operator SDK
Container Registry Quay.io Red Hat Quay
Container Platform Kubernetes Red Hat OpenShift
Observability
(Metrics, Tracing, Logging)
OpenTelemetry, Prometheus, Loki, Tempo, Grafana OpenShift Logging Operator, OpenShift Observability Operator

Why OpenShift? The platform was chosen for validation because of its security certifications and proven track record in critical environments across multiple industry verticals. OpenShift has been extensively tested and proven in mission-critical environments, including financial markets and other regulated industries.

No Vendor Lock-in: This is a community project. While components were validated using Red Hat supported downstream versions, you are completely free to use upstream community versions without any harm. No vendor dependency is required.

Ready to Get Started?

Deploy locally with Minikube or explore the documentation