How jensroland/kegstand works
Main Components
a. CLI Layer (Command Interface)
• Main CLI commands (new, build, deploy, teardown)
• Configuration handling components
• To template system (*.tmpl files)
b. Infrastructure Layer (AWS CDK Integration)
• REST API Backend Stack
• REST API Gateway Stack
• Lambda Function handlers
• Integration with AWS CDK
c. Project Template Structure
• Standard project layout
• API organization pattern
• Build system integration (uv/Poetry support)
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
• CLI Layer │ │Infrastructure │ │ AWS Cloud │
• > │ Layer │ -> │ Resources │
• ┘ └─────────────────┘ └─────────────────┘
Component Details
CLI Layer (Left):
• Template files with document symbols
• Configuration handling
Infrastructure Layer (Middle):
• CDK Stack components
• Build process
• Template processing
AWS Cloud (Right):
• API Gateway
• Lambda Functions
• Other AWS services
Key Relationships
a. Command Flow:
• CLI commands → Infrastructure Layer
• Infrastructure Layer → AWS Resource Creation
b. Build Process:
• Project Template → Built Lambda Functions
• Configuration → Infrastructure Deployment
c. Runtime Flow:
• API Gateway → Lambda Functions
• Service Dependencies
Important Elements to Highlight
• Template-based project generation
• Build system flexibility (uv/Poetry)
• AWS resource provisioning
• API Gateway configuration
• Lambda function deployment