How galdor/boulevard works
Main Components Identification
a. Core Components (pkg/boulevard):
• Format String Handler
• Module System
• Spill Buffer
• Templates Engine
b. Network Components (pkg/modules):
• HTTP Server Module
• TCP Server Module
• FastCGI Client
• Network Utilities
c. Service Layer (pkg/service):
• ACME Certificate Management
• Configuration Management
• Control API
• Module Management
┌─ Client Layer ─────────────────────────┐
• HTTP Clients │ TCP Clients │ FastCGI │
• ┴─────────────┴───────────┘
• ↓ ↓ ↓
┌─ Frontend Layer ──────────────────────────────┐
• TCP Listeners │ TLS Termination │ ACME Cert │
• ┴─────────────────┴────────────┘
• ↓ ↓ ↓
┌─ Core Processing Layer ────────────────────────┐
• HTTP Server │ TCP Server │ Reverse Proxy │
• Auth (Basic/Bearer) │ Request Handling │
• ┘
• ↓ ↓ ↓
┌─ Backend Services Layer ──────────────────────┐
• FastCGI │ Static Files │ Upstream Services │
• ┘
Key Relationships to Highlight
a. Request Flow:
• How requests enter through listeners
• TLS termination points
• Routing through the HTTP/TCP servers
• Demonstrate backend service connections
b. Control Flow:
• Control API paths
• Configuration management flow
• Certificate management process
Implementation Details
• HTTP Server Module (pkg/modules/httpserver)
• Access Logger
• Authentication (Basic/Bearer)
• Request Handlers
• Path Patterns
• Actions (FastCGI, Redirect, Reverse Proxy, etc.)
• TCP Server Module (pkg/modules/tcpserver)
• Connection Management
• Listeners
• Status Monitoring
• Service Layer (pkg/service)
• Configuration Management
• Control API
• Module Management
• ACME Integration
Additional Notes
• Version information and date
• Experimental status of the project
• Configuration file relationship (cfg/*.yaml)
• Command-line interface points (cmd/boulevard-cli)