How wundergraph/cosmo works
Main Components
The system should be divided into these core components:
a. Control Plane (Management Layer):
• Schema Registry
• Composition Service
• Authentication/Authorization
• Analytics & Metrics Collection
• Configuration Management
• User Management
b. Data Plane (Runtime Layer):
• Router Service
• GraphQL Federation Engine
• Metrics Collection
• Tracing System
c. Storage Layer:
• PostgreSQL (for control plane data)
• ClickHouse (for analytics)
• Redis (for caching)
• MinIO/S3 (for blob storage)
d. Supporting Services:
• Keycloak (authentication)
• OTel Collector (telemetry)
• CDN Server
• Studio (Web UI)
Component Relationships
a. External Interactions:
• Clients → Router
• CI/CD Systems → Control Plane
• Developers → Studio UI
b. Internal Data Flow:
• Router → Control Plane (configuration updates)
• Router → OTel Collector (metrics/traces)
• Control Plane → Storage Layer
• Studio UI → Control Plane
• CDN Server ↔ Storage Layer
Key Architectural Patterns
Patterns:
• Event-driven architecture for real-time updates
• Microservices architecture for component isolation
• API Gateway pattern for the router
• Publisher/Subscriber pattern for events
• Cache-aside pattern for performance
Component Details
• Service name
• Primary function
• Key technologies used
• Critical dependencies
Security Boundaries
Indicate:
• Authentication boundaries
• Authorization checkpoints
• Network security zones
• Data encryption points
Scaling Points
Highlight:
• Horizontally scalable components
• Load balancing points
• Caching layers
• Database replication
Monitoring Points
Mark:
• Metrics collection points
• Trace aggregation
• Log collection
• Health check endpoints
Data Layer (bottom)
Remember to emphasize the federated nature of the system and how it handles GraphQL schema composition and request routing.