Scope: Everything accumulated across this project — Hummingbird 2.x internals, clean architecture patterns, MCP server design, deployment strategy, and the
hummingbird-knowledge-serverimplementation decisions. Written for engineers who want production-grade output, not tutorial code.
| # | Topic | What’s covered |
|---|---|---|
| 1 | Introduction | Why Swift for servers, the dependency stack, Hummingbird overview, and the critical 1.x → 2.x migration break |
| 2 | Core Concepts | Application setup & entry point, routing, request/response handling, middleware |
| 3 | Concurrency & Services | Swift Structured Concurrency pitfalls, actor safety, task cancellation, service lifecycle |
| 4 | Integrations | Database (PostgresNIO), authentication & JWT, WebSockets, background jobs |
| 5 | Testing & Deployment | HummingbirdTesting modes, fake repositories, Docker multi-stage builds, performance tips |
| 6 | Pitfalls Reference | All 20 pitfalls ranked by severity — quick lookup table |
| 7 | Clean Architecture | Layer model, dependency injection via RequestContext, the controller pattern, service layer, repository pattern, error handling |
| 8 | MCP Server | MCP protocol, transport implementation, tool design, auto-update & self-healing, deployment modes |
| 9 | References | Key links — GitHub repos, docs, specs, forums |
Last updated: February 2026 Covers: Hummingbird 2.x · Swift 6.0 · MCP Spec 2025-06-18 · hummingbird-knowledge-server v0.1.0