Plugin architecture for a traffic-management integration platform

Situation. Teledyne builds integration platforms for traffic-management systems. Such a platform has to run in very different environments — from fully air-gapped to cloud — and connect to different systems per client. The challenge: one platform you can roll out across all those environments and extend per client, without custom work in the codebase each time.

Approach. I worked on the platform as a senior Java developer and co-designed and built the plugin architecture.

In concrete terms:

• A plugin architecture for multiple integration types, so a new connection is added as a separate plugin;
• Event routing and processing of SSE streams in a reactive, high-throughput pipeline (Project Reactor, Kafka);
• Client-specific extensions through Groovy scripting, without touching the core;
• Angular frontend;
• Containerised deployments reusable across all environments, from air-gapped to cloud;
• CI/CD with GitHub Actions.

Result. One integration platform that runs in both air-gapped and cloud environments, where new integrations and client-specific logic are added as a plugin or script instead of as custom work in the codebase.