Going Full Silo - Using Serverless to Build for Dev Simplicity
summary
Company builds wearable barcode scanners and runs a serverless multi-tenant backend by deploying the full stack into separate AWS accounts per customer, giving 3,500 AWS accounts with roughly 200 Lambdas per account (north of 600,000 functions total) and about 70 million events/month. CI creates per-PR sandbox accounts, runs the full test suite there, and then deploys through staged pipelines; architecture reduces accidental cross-tenant access and makes developer sandboxes identical to production while increasing observability and account-management complexity.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 1:52Device data and SaaS offering
- 4:45Tenant isolation explained
- 7:17Architecture overview
- 9:00Benefits of full silo
- 11:31Developer sandbox environments
- 13:40CI/CD pipeline process
- 15:48Pros and cons summary
- 16:53Q&A and closing
related talks
47mServerless in production, an experience report
41mCI/CD in the Serverless Era
39mServerless in production, an experience report
54mServerless Architectures: no servers allowed!
29mGoing Serverless
01h 02mServerless in production, an experience report
51mTaking Serverless to the Next Level
01h 02mFrom Monolith to Serverless
