How mt-empty/workflow works
Main Components Identification
a) Core Components:
• Workflow Engine (Main Service)
• Redis Queue (Task Queue)
• PostgreSQL Database (State Storage)
• Event Triggers System
• Task Execution System
b) Supporting Components:
• CLI Interface
• File System (for workflow definitions and logs)
• Docker Container Environment
[CLI Interface] --> [Workflow Engine]
[YAML Workflow Definitions] --> [Parser]
[Event Trigger System] <--> [Workflow Engine] <--> [Task Execution System]
[Redis Queue] <--> [Workflow Engine] <--> [PostgreSQL Database]
Component Details and Relationships
• Rectangles: Main services (Engine, CLI)
• Hexagons: Event triggers and tasks
Key Processes to Highlight
Main workflow processes:
Workflow Definition --> Parser --> Engine
Event Trigger --> Engine --> Task Queue --> Task Execution
Specific Implementation Details
Technical details in annotations:
• Rust-based implementation
• Docker container deployment
• Database migrations using Diesel
• Redis for task queuing
• File-based event triggers and task definitions
Distributed Architecture (Future State)
• Multiple engine instances
• Round-robin load balancing
• gRPC streaming
• Container orchestration
Additional Elements
• Log storage and management
• Environment configuration flow
• Container networking
• Error handling paths
• Task failure handling
The file-based configuration system
For this specific project, focus on showing how the engine handles the flow from event triggering through task execution, as this is the core functionality of the system. Also highlight the CLI interface as it's the primary way users interact with the system.