How boostercloud/booster works
Main Components
a) Core Framework Layer:
• Command Handling System
• Event Processing System
• Entity Management
• Read Model System
• GraphQL API Layer
• Authentication/Authorization System
• Health Monitoring System
b) Provider Infrastructure Layer:
• AWS Implementation
• Azure Implementation
• Local Development Implementation
c) CLI and Development Tools:
• Project Generation
• Code Generation
• Deployment Management
Key Relationships
a) Data Flow:
• Command → Event → Entity → Read Model pipeline
• GraphQL query/mutation/subscription flows
• Event sourcing and CQRS pattern implementation
b) Infrastructure Integration:
• Provider-specific service mappings
• Serverless function deployment paths
• Database and storage connections
[User/Client Layer]
• ▼
[GraphQL API Layer]
• ┬─────────────────────┐
• ▼ ▼ ▼
[Command Handler] [Query Handler] [Subscription Handler]
• ▼ │ │
[Event Processing] │ │
• ▼ │ │
[Entity Store] ──────────►│ │
• ► [Read Models] ◄───────┘
• ▼
[Infrastructure Layer (AWS/Azure/Local)]
Important Details
a) Framework Features:
• Event sourcing mechanism
• CQRS implementation
• Authentication/Authorization flow
• Health monitoring system
• Rocket extensions system
b) Infrastructure Elements:
• Serverless functions
• Database systems
• Message queues
• API gateways
• Storage services