Swift NIO, Vapor, and Server Concurrency
summary
Explains why Swift NIO replaces a thread‑per‑connection model in Vapor, moving from POSIX threads and libdispatch blocking to an evented nonblocking I/O core that lets a single thread serve many connections, issue multiple external API calls concurrently, and avoid idle CPU while waiting for responses. Shows integration into Vapor 3, uses futures for asynchronous chaining, leverages built in HTTP and WebSocket parsers, and reports concrete gains in resource efficiency and ecosystem reliability.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:17IPHONE POWER
- 3:23IPHONE DEVELOPMENT
- 3:58SERVER DEVELOPMENT
- 7:51PHONE CONCURRENCY
- 9:06VAPOR 1.0
- 9:33P_THREAD
- 11:38VAPOR 20 - DISPATCH
- 12:56NON-BLOCKING I/O (NIO)
- 17:04FUTURES
related talks
27mFull Stack Development with Swift and Vapor
41mGetting started with Server-Side Swift and Vapor
22mEvent driven networking for Swift
30mSwift on the Server
41mServer-Side Swift State of the Union
36mFull stack development with Swift and Vapor
19mServer-side Swift Using Vapor
31mGetting Started With Server Side Swift
