Getting started with Server-Side Swift and Vapor
summary
Argues that using Vapor 3 and SwiftNIO + Fluent + SQLite gives a compact, type-safe server stack and demos building a full CRUD API in ~10 minutes with routes, Codable models, migrations and async saves/queries that actually work. Claims typical Vapor app uses ~6 MB RAM and cites one agency cutting backend costs ~70–80% after migrating off PHP. Notes real downsides: futures/promises learning curve, immature Linux tooling and occasional Foundation gaps, but the demo is complete and functional.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:23Introduction
- 2:34What is Vapor
- 3:11History of Vapor
- 5:14My involvement with Vapor
- 6:58Why use Swift
- 9:03Developer happiness
- 13:31Why Vapor
- 16:24Vapor Cloud
- 17:00Downsides to Swift
- 19:37Live Coding
- 26:10Database Interaction
- 32:50Getting a Single User
- 34:02Searching Users
related talks
36mFull stack development with Swift and Vapor
27mFull Stack Development with Swift and Vapor
47mServer Side Swift with Vapor
31mGetting Started With Server Side Swift
19mServer-side Swift Using Vapor
34mServer Side Swift
39mBYOB: Build Your Own (Swift) Backend. Server-Side Swift beyond CloudKit
41mServer-Side Swift State of the Union