Battle of the Giants: Vapor vs Hummingbird which one should you choose?
summary
Compares Vapor and Hummingbird as Swift HTTP servers with concrete differences: routing and controllers work the same, both support Fluent ORM (Hummingbird via a separate HummingbirdFluent package), middleware is comparable, and both deploy easily with Docker or Lambda. Vapor is opinionated with a helpful CLI and a larger community, making faster onboarding; Hummingbird is flexible, type-safe request contexts and better NoSQL/Kitten wiring for custom stacks. Authentication and request-context handling differ materially; performance depends on SQL and query design rather than framework choice.
AI-written summary · about
chapters (19)
- 0:00My journey to backend
- 1:03Confusing backend choices
- 1:43Discovering server-side Swift
- 2:52The decision framework
- 4:25Disclaimers and personal view
- 6:51Similarities of frameworks
- 7:36Routing in Vapor and HB
- 9:36Persistence and Fluent
- 10:46Code example comparison
- 12:38Understanding middleware
- 14:14Open source and support
- 15:34Key differences
- 17:47Persistence differences
- 18:54Opinionated vs flexible
- 20:44Authentication approaches
- 22:54Context and OAuth
- 25:32Performance and deployment
- 28:32Summary of trade-offs
- 29:11Conclusion and Q&A
related talks
09mIntroduction to Hummingbird 2
19mServer-side Swift Using Vapor
27mFull Stack Development with Swift and Vapor
36mFull stack development with Swift and Vapor
41mGetting started with Server-Side Swift and Vapor
35mSwift, Server-Side, Serverless
34mServer Side Swift
31mGetting Started With Server Side Swift