$ show vogler75/automation-gateway
Automation Gateway is a reactive, configuration-driven bridge for industrial protocols (OPC UA, MQTT, PLC4X) that routes real-time process data to multiple time-series databases (InfluxDB, IoTDB, OpenSearch, Cassandra, PostgreSQL, etc.) and exposes it via GraphQL, MQTT, and OPC UA servers. The system runs as a single JVM or GraalVM native binary, orchestrated through YAML configuration files that define driver instances, logger sinks, and server endpoints. Its core architecture is built on Vert.x event bus for internal pub/sub messaging, with abstract base classes (DriverBase, LoggerBase) enabling consistent extension for new protocols or data stores. The gateway does not persist data itself; it acts as a real-time router with configurable buffering and queue reliability (memory-mapped disk queue). Key entry points include `App.kt` for the main application and `GraphQLServer.kt` for the administrative API, which supports JWT authentication, health checks, and dynamic component management. External dependencies include Eclipse Milo (OPC UA), HiveMQ MQTT client, PLC4X, Apache IoTDB Thrift, InfluxDB HTTP client, and various database drivers. The codebase is mature (v1.38) with active development, but carries some technical drift in the form of deprecated features still present in source code and a large set of reflection configurations for GraalVM native-image that require careful maintenance.
The LLM identified 3 files worth highlighting for reuse:
Implements a disk-backed queue using memory-mapped files for reliable data buffering. This component can be extracted and reused in any application that needs crash-safe, high-throughput write buffering for time-series data, independent of the gateway's domain logic. It demonstrates non-obvious use of Java NIO MappedByteBuffer for durable queuing.
Provides a bounded in-memory queue using an ArrayBlockingQueue, designed as an alternative to the disk queue. This is a clean, thread-safe implementation of the producer-consumer pattern specific to logging frameworks, but its interface (ILoggerQueue) makes it pluggable. Reusable in any Vert.x application requiring a configurable queue backend.
Core data class for representing hierarchical topics (e.g., 'opc/system/path/Objects/Demo/...'). Encapsulates parsing, serialization, and routing logic. This component is self-contained and could be extracted as a library for any system that uses hierarchical topic routing (e.g., MQTT, OPC UA node paths). It demonstrates clean separation of concerns and robust string parsing.