How to build a social network entirely on serverless
summary
Yubl migrates from a monolith to serverless by publishing state changes to Kinesis and wiring Kinesis + Lambda + API Gateway for search, feeds, recommendations, push and BI; migration finishes in about six months for a million users. Resulting system runs around 200 functions, jumps to 80–100 deployments/month, uses BigQuery/Athena, SNS, Redis and Neo4j for graphs, and replaces a $3,000/month Mixpanel bill with cent‑level per‑query costs.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:42Hubble
- 1:41Why
- 8:13Events
- 8:46Microservices
- 9:35cascade failures
- 10:28eventdriven architecture
- 11:43workflow engine
- 14:08one repo per function
- 14:47one repo per microservice
- 17:56migration pattern
- 20:22cost saving
- 27:13recommendation feature
- 30:13more scalable
related talks
29mHow to build a social network on serverless
44mHow to build a social network entirely on serverless
24mServerless gives you wings
39mServerless in production, an experience report
33mBuild a social network with Serverless and GraphQL
01h 02mServerless in production, an experience report
01h 02mFrom Monolith to Serverless
30mThinking Serverless: From User Request to Serverless Solution
