How jorisvink/kore works
Main Components
a) Core Server Components:
• Worker Process Manager
• TLS/Security Layer
• Event-driven Architecture (epoll/kqueue)
• HTTP/1.1 Server
• WebSocket Server
• Module System
b) Extension Systems:
• Python Runtime Integration
• Lua Runtime Integration
• PostgreSQL Connector
• CURL Integration
• ACME Certificate Manager
c) Security Components:
• Privilege Separation System
• Seccomp/Pledge Sandbox
• Key Management Process
• TLS Backend
┌─ External Clients Layer ─┐
• (HTTP/WS/TLS) │
┌─ Security Layer ────────┐
• (Privilege Sep.) │
┌─ Core Server Layer ─────┐
• (Worker Processes) │
┌─ Extension Layer ───────┐
• (Python/Lua/DB/etc.) │
Key Relationships to Highlight
• Privilege separation between components using distinct boundaries
• Worker process distribution
• Demonstrate the module loading system
• Connection handling flow
• Integration points with external services
Important Elements
a) Process Flow Indicators:
• Request handling path
• Worker process communication
• Module loading/reloading
• Security boundary crossing
b) Component Details:
• Worker process pools
• Event handling system
• Module system
• Security containers
Specific Implementation Details
• The event-driven architecture
• Per-CPU worker process distribution
• Privilege separation boundaries
• Module hot-reloading capability
• Security sandbox implementation