Full stack development with Swift and Vapor
summary
Argues that Swift is production-ready on the server, using Vapor 4 atop Swift NIO to build a REST backend; demonstrates a reminders app with shared models via a Swift Package, three route handlers (create, list, fetch), and type-safe migrations that handle dates with Codable. Claims typical service uses ~6 MB memory footprint, deploys on Ubuntu/Docker, cites companies using server-side Swift and an 80% cost improvement vs PHP for some migrations.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:30Audience participation
- 2:00Backend and frontend teams
- 3:10Apps
- 5:30Why Swift
- 6:40Javascript
- 7:05What is Vapor
- 8:22Why use Vapor
- 10:35Why use Swift
- 11:50Deploying Swift
- 12:20is Swift ready for production
- 13:55Companies using Swift in production
- 15:40Demo
- 16:35Packages
- 21:25Routes
- 27:35Date
- 28:15Next steps
related talks
27mFull Stack Development with Swift and Vapor
41mGetting started with Server-Side Swift and Vapor
19mServer-side Swift Using Vapor
31mGetting Started With Server Side Swift
34mServer Side Swift
30mSwift on the Server
41mServer-Side Swift State of the Union
17mThe Success Story of Server-Side Swift at Cultured Code
