How oxidecomputer/buildomat works
Main Components Overview
a. Core Components:
• Buildomat Server (Central API Server)
• Client Components (CLI & Library)
• Agent System
• Database Layer
b. Factory Systems:
• AWS Factory
• Lab Factory
c. GitHub Integration:
• GitHub Server
• GitHub Database
• Webhook Processing System
Component Relationships
a. Control Flow:
• GitHub webhooks → GitHub Integration Server
• GitHub Integration Server → Core Server
• Client Tools → Core Server
• Factories → Core Server
• Agents → Core Server
b. Data Flow:
• Core Server ↔ Database
• GitHub Integration ↔ GitHub Database
• Build Artifacts Flow (Agent → Server → Storage)
Specific Implementation Details
Technical elements:
a. Server Components:
[GitHub Webhooks] → [GitHub Integration Server]
• ↓
[Core API Server] ← → [Database]
• ↑ ↑
[Factories] [Agents]
b. Factory Implementation:
[Factory Manager]
• ↓
[Resource Provisioning]
• ↓
[Worker Management]
Detailed Component Breakdown
For each major component, show:
a. Server:
• API endpoints
• Job management
• Worker coordination
• File management
b. Factories:
• Resource provisioning
• Instance lifecycle
• Worker coordination
c. Agent:
• Job execution
• File transfer
• Security components
Cross-Cutting Concerns
Aspects:
• Authentication flows
• Security boundaries
• Monitoring points
• Scaling components
The security boundaries between components
Remember to highlight the ephemeral nature of workers and the job execution lifecycle, as these are central to the system's design philosophy.