Server Side Swift
summary
Argues that Swift is fast enough for server workloads and that developer productivity matters more than microbenchmarks, citing company expenses where server costs are ~2% of monthly spend. Demonstrates a small blog backend built as value-type models, repository storage, controllers that return JSON views, and a router/middleware chain that composes apps. Compares Vapor (feature-rich, generators) and Kitura (lightweight, Node-like) as usable frameworks, recommends adopting OpenSwiftStandards and the emerging Swift server APIs for better compatibility and code reuse.
AI-written summary · about
chapters (9)
- 0:00Introduction to server Swift
- 4:00Roadmap for the talk
- 5:17Why consider Swift for servers
- 9:41Understanding HTTP protocols
- 14:15Abstraction and standards
- 17:39Applying MVC to the server
- 23:33Routing and architecture
- 28:51Framework overview
- 31:25Future vision for Swift
related talks
41mServer-Side Swift State of the Union
36mFull stack development with Swift and Vapor
41mGetting started with Server-Side Swift and Vapor
39mBYOB: Build Your Own (Swift) Backend. Server-Side Swift beyond CloudKit
24mServer-Side Swift from Scratch
39mWhy Is Swift So Much Better On Server?
27mFull Stack Development with Swift and Vapor
30mSwift on the Server
