Serverless WebSockets at Scale
summary
Evaluation of AWS options leads to a custom hybrid: a serverless publishing path (API Gateway → Lambda → DynamoDB → SNS) plus an ECS-based websocket fleet named Puppy that uses ElastiCache pub/sub to fan out to millions of clients. AppSync hits auth, caching and race-condition limits; API Gateway websockets can’t cheaply broadcast; IoT has auth quirks. Load tests target 3 million connections, initial run fails but health-check driven Route 53 failover and proactive task draining fix it, delivering 0.7 ms p90 latency and high availability.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:08Requirements
- 4:57Why WebSockets
- 8:28WebSockets Website
- 9:27Graphql
- 10:37Authentication
- 12:14QuerySubscribe
- 13:51Global Deployment
- 15:02Caching
- 18:54Appsync
- 24:37Architecture
- 30:11Questions
related talks
51mArchitecting for Hyperscale with AWS: Navigating Real-world Serverless Challenges
34mPower real-time serverless applications with GraphQL and AWS AppSync
51mServerless architectural patterns
29mBuild highly scalable serverless applications on AWS
40mThe serverless startup
49mServerless Architectural Patterns and Best Practices
54mServerless Architectures: no servers allowed!
29mHow to build a social network on serverless