How tarmac-project/tarmac works
Main Components
a. Core Components:
• Tarmac Host Server
• WebAssembly Engine
• Function Registry
• Route Handler
• Callback System
• Configuration Manager
b. Integration Components:
• Key-Value Store Interface
• SQL Database Interface
• HTTP Client Interface
• Metrics System
• Logging System
c. External Services Support:
• Redis
• MySQL/PostgreSQL
• Cassandra
• Consul
• Prometheus
Layer 1: Client Interface Layer
• HTTP Endpoints
• Scheduled Task Triggers
• Boot Triggers
Layer 2: Tarmac Host Layer
• Route Handler
• Configuration Manager
• Function Registry
Layer 3: WebAssembly Runtime Layer
• WASM Engine (waPC)
• Function Instances
• Callback Handler
Layer 4: Core Capabilities Layer
• Key-Value Store Interface
• SQL Interface
• HTTP Client
• Logging
• Metrics
Layer 5: External Services Layer
• Databases
• Caches
• Monitoring Systems
Key Relationships
a. Request Flow:
• Client → HTTP Handler → WASM Function → Callback System → External Services
• Scheduler → WASM Function → Callback System → External Services
b. Configuration Flow:
• tarmac.json → Configuration Manager → Function Registry → WASM Engine
c. Integration Points:
• WASM Functions ↔ Callback System
• Callback System ↔ Core Capabilities
• Core Capabilities ↔ External Services
Implementation Notes
• Maintain consistent spacing and alignment
• Brief annotations for complex interactions
• Creating separate detailed views for specific subsystems
• Version information and date
Focus Areas
• WebAssembly-centric architecture
• Flexibility in supporting multiple functions
• Built-in capabilities
• Demonstrate the language-agnostic nature
• Scalability aspects