How google/turbinia works
Component Relationships
Client Layer → API Server → Server Layer → Worker Layer
• ↓
• Storage & State Management
Specific Implementation Details
Key architectural elements:
a) Request Flow:
• Client submits evidence → API Server validates → Server creates jobs → Tasks distributed to workers
b) Worker Processing:
• Parallel task execution
• Docker container boundaries
• Evidence feedback loop where new evidence is fed back into the system
c) Integration Points:
• External forensic tools (Plaso, TSK, etc.)
• Cloud service connections
• Monitoring systems (Prometheus/Grafana found in /monitoring)
Technical Stack Indicators
• Frontend: Vue.js (based on /web directory)
• API: FastAPI (based on openapi.yaml)
• Message Queue: Kombu/Celery
• Storage: Redis
• Containerization: Docker
Deployment Context
Deployment options as a separate section:
• Cloud deployment
• Local deployment
• Hybrid deployment
Additional Elements
Include:
• Version/state indicators (Alpha release)
• Security boundaries
• Monitoring points
• Error handling paths