From iOS- to Vapor developer
summary
Claims that Vapor can run production workloads after six months of real use include concrete results: Vapor in production for 6 months, deployed on Vapor Cloud, serving 25 customer projects with hosting costs falling. Tooling and practices listed are specific: use MySQL, Leaf templates, Sentry or sparklysnag for error reporting, SwiftyBeaver logging, Sorcery to remove boilerplate, and CircleCI Linux builds to catch porting issues. Notes Linux quirks, package churn, and migration pain.
AI-written summary · about
chapters (32)
- 0:00Introduction
- 2:32Swift pros
- 6:02Swift cons
- 9:45Swift web frameworks
- 14:15Number of users
- 15:02Performance
- 15:54Crash handling
- 16:50Platforms
- 17:22Foundation
- 17:49Xcode
- 18:20Thirdparty frameworks
- 18:46User interfaces
- 19:00Persistence
- 19:48Security
- 20:30Consumer
- 21:05Backend
- 21:39Documentation
- 21:56Community
- 22:16Foundation for Linux
- 22:54Reporting
- 23:14CI
- 23:59AP Isis
- 24:25Blackbox testing
- 24:42Security headers
- 25:08Vapor Cloud
- 25:45Backend development
- 28:14Updates
- 28:38Cloudant
- 29:23How have we been using Cloudant
- 29:36Memory footprint
- 30:12Resources
- 30:23Swift Con
related talks
27mFull Stack Development with Swift and Vapor
19mServer-side Swift Using Vapor
41mGetting started with Server-Side Swift and Vapor
36mFull stack development with Swift and Vapor
32mLessons learned from running a SaaS entirely on Swift Vapor
27mShipping a SaaS backend using Vapor
21mThe Adventures and Misadventures of Building a Trivia app with Vapor
47mServer Side Swift with Vapor