How brexhq/substation works
Main Components
a. Core Processing Components:
• Message Processing Engine (message/)
• Transform Engine (transform/)
• Condition Engine (condition/)
• Configuration Manager (config/)
b. Infrastructure Components:
• AWS Services Integration Layer
• HTTP Services Layer
• Storage Systems Interface
• Metrics and Monitoring
Key Architectural Elements
a. Input Sources:
• API Gateway
• AWS Services (Kinesis, SQS, Lambda)
• File Systems
• Standard Input
b. Processing Pipeline:
• Message Parsing
• Transformation Logic
• Condition Evaluation
• Enrichment Services
c. Output Destinations:
• AWS Services (S3, DynamoDB, etc.)
• HTTP Endpoints
• Standard Output
• File System
[Input Layer]
• ▼
[Configuration Management]
• ▼
[Core Processing]
• Message Processing
• Transform Engine
• Condition Engine
• Enrichment Services
• ▼
[Output Layer]
Detailed Component Relationships
• Configuration Management ↔ Core Processing
• Transform Engine ↔ External Services
• Message Processing ↔ Transform Engine
• Input Sources → Message Processing
• Transform Engine → Output Destinations
Implementation Details
• Serverless deployment option
• AWS service integration points
• Configuration flow using Jsonnet
• Security boundaries and encryption points
Deployment View
• AWS deployment architecture
• Container deployment options
• Local development setup
Notes
• Keep the main flow clear and centered
• Related components visually
• Version/configuration management flow
• Scale-out possibilities
• Extensible data processing
• Cloud-native routing
• Schema flexibility
• Enrichment capabilities
• Serverless deployment options