Serverless @ 30k Feet
summary
Ryanair’s tech team explains why they adopted a Serverless-first approach on AWS, describing concrete use cases and the AWS Serverless services they use to meet business requirements. The talk reviews pros and cons encountered, tooling, and criteria Ryanair uses to choose between serverless and non-serverless architectures, emphasizing the need for flexibility to move between them.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:06Ryanair context and challenges
- 3:52What Serverless means
- 5:58AWS Serverless resources
- 6:19DynamoDB as Serverless DB
- 7:44Aurora Serverless costs
- 11:36QLDB for immutable logs
- 13:18Cognito for user management
- 15:26ECS Fargate for containers
- 16:30AWS Lambda as star service
- 19:46Useful Serverless tools
- 20:06Legacy app migration case
- 21:10Serverless frontend architecture
- 22:13Serverless API without Gateway
- 24:43Serverless summary and tips
- 26:31Ryanair conclusions and future
- 29:20Q&A
related talks
52mWhy Serverless?
52mThe Serverless Journey
55mLive Serverless
33mAccelerating Towards Serverless-First with the Value Flywheel Effect
46mServerless approach to software architecture and development
20mWhy Serverless Architecture is Changing Software Development
07mAndrea Passwater, Serverless | ServerlessConf 2018
34mThinking serverless: From business problem to Serverless solution
