Thinking Twice About Migrating to Serverless
summary
Examines migrating a Java/Spring monolith to serverless (AWS Lambda, managed databases, messaging) and argues it requires full re-architecture: turning services into stateless functions forces redesign of authentication, state handling, testing and CI/CD, and increases cloud-provider coupling. Describes using infrastructure-as-code templates plus functions and managed services, shares security and operational gaps found in experiments, and reports that changed costs, deployment complexity and team workflows often lead teams to cancel or reshape migrations.
AI-written summary · about
chapters (6)
- 0:00Serverless migration intro
- 3:11Serverless architecture
- 6:01Migrating challenges
- 9:15Security and legacy
- 11:22Business case
- 13:52When serverless fails
related talks
45mPatterns & practices for developing enterprise-scale serverless applications
31mWhen Bad Architectures Happen To Good People: Migrating Legacy Systems To Serverless
41mYou Don’t Want to Build a Serverless Monolith
01h 00mMicroservices and Serverless
51mConfusion In The Land Of The Serverless
04mWhat if serverless was real?
01h 04mMigrating to Serverless - an experience report
55mConfusion In The Land Of The Serverless