Migrating to Serverless - an experience report

on YouTube ↗01h 04m

" summary

Migrated a large collaboration platform from Heroku to AWS Lambda, cutting operational costs and improving scalability while deleting about one third of application code. Uses Lambda, API Gateway, S3, Cognito and CloudWatch for centralized logging, per-function versioning and A/B testing; billing is per-100ms, exposing fine-grained cost and performance per function. Built small single-purpose exporters (PDF, SVG) and a Web API; works but has limits: ~100–200ms extra latency, 5-minute execution ceiling, no enterprise SLA and potential vendor lock-in.

AI-written summary · about

" chapters (20)

1. 0:00Introduction
2. 6:57Reserved capacity
3. 8:15Freezing up
4. 12:35Three types of toys
5. 13:55Services
6. 15:11Deployment
7. 16:02Create API
8. 18:55AWS Console
9. 20:41Scaling
10. 28:11Time to recover
11. 29:26Multiversioning
12. 30:46Version push
13. 34:08Embrace the platform
14. 34:40Authorization
15. 35:18Distributed Authentication
16. 40:56Stateless
17. 46:09Strengths
18. 51:54Weaknesses
19. 54:03Other services
20. 58:15Opportunities

" related talks

• 39mServerless in production, an experience reportYan Cui · Codemotion Milan 2017
• 01h 02mServerless in production, an experience reportYan Cui, Domas Lasauskas · NDC London 2018
• 54mServerless Architectures: no servers allowed!Antons Kranga · JavaDay Lviv 2016
• 45mPatterns & practices for developing enterprise-scale serverless applicationsSheen · Agile India 2025
• 42mServerless Tales from the TrenchesPeter Sbarski · GOTO Chicago 2018
• 47mServerless in production, an experience reportYan Cui · Build Stuff 2017
• 42mAWS Lambda from the trenchesYan Cui · code.talks 2017
• 21mMigrating Legacy Backends to Serverless in ParallelRumesh Eranga · FOSSASIA Summit 2017