How uber-go/cadence-client works
Main Components
a. Core Components:
• Workflow Engine
• Activity System
• Worker System
• Client Interface
• Internal Services
b. Supporting Components:
• Authentication System
• Metrics & Monitoring
• Serialization Services
• Cache System
• Auto-scaling Components
┌─ Application Layer ─────────────────────────────┐
• ┌─ Client APIs ──┐ ┌─ Workflow Engine ──┐ │
• Domain │ │ - State Machine │ │
• Workflow │ │ - Context │ │
• Activity │ │ - Error Handling │ │
• ┘ └──────────────────┘ │
• Worker Layer ──────────────────────────────┐ │
• ┌─ Worker Components ─┐ ┌─ Activities ──┐ │ │
• Task Handlers │ │ - Execution │ │ │
• Pollers │ │ - Heartbeat │ │ │
• Auto-scaler │ │ - Recovery │ │ │
• ┘ └───────────────┘ │ │
• Infrastructure Layer ────────────────────┘ │
• ┌─ Common Services ─────────────────────┐ │
• Authentication │ │
• Metrics │ │
• Serialization │ │
• Caching │ │
• ┘ │
• ┘
Key Relationships to Highlight
• Bidirectional communication between Client APIs and Workflow Engine
• Task flow from Worker Components to Activities
• How Infrastructure Services support all upper layers
• Integration points with the main Cadence server
Technical Details
• YARPC communication paths
• Thrift/Proto serialization flows
• Cache interaction patterns
• Auto-scaling decision flows