C4 Workflow Diagram - Level 2: Container Workflows
CODITECT Context Intelligence Platform
Diagram Level: 2 (Container) Focus: Workflows between containers (API, databases, workers) Audience: Developers, DevOps Purpose: Understand inter-container communication
Workflow 1: Hybrid Search Execution
Performance: p95 <100ms
Workflow 2: Create Conversation with Background Embedding
Duration: User sees response in ~150ms, embedding completes in ~2s
Workflow 3: GitHub Webhook with Correlation
Duration: <500ms webhook processing, 1-2s correlation
Workflow 4: Authentication & Authorization Check
Workflow 5: Team Analytics Calculation
Cache Strategy: 1 hour TTL for historical data, no cache for current day
Workflow 6: WebSocket Real-Time Updates
Scaling: Redis Pub/Sub for horizontal scaling across multiple API pods
Container Communication Summary
| From Container | To Container | Protocol | Port | Purpose |
|---|---|---|---|---|
| Web App | API Layer | HTTPS | 443 | User actions |
| API Layer | PostgreSQL | PostgreSQL | 5432 | Data queries |
| API Layer | Weaviate | GraphQL/HTTP | 8080 | Semantic search |
| API Layer | Redis | Redis Protocol | 6379 | Cache + queue |
| API Layer | WebSocket Manager | Internal | N/A | Real-time events |
| Celery Worker | PostgreSQL | PostgreSQL | 5432 | Data updates |
| Celery Worker | Weaviate | GraphQL/HTTP | 8080 | Vector upsert |
| Celery Worker | OpenAI API | HTTPS | 443 | Embeddings |
| Celery Worker | Redis Pub/Sub | Redis Protocol | 6379 | Event broadcast |
Next Level: Component Workflows
The Container workflows show how containers interact. The next level (Component Workflows) will show workflows within containers at the component level (services, repositories, endpoints).
See: c4-l3-workflow-component.md
Diagram Maintained By: Engineering Team Last Updated: 2025-11-26