Server-less architecture in the wild
summary
A production project at D and Thomas Cook runs a serverless GraphQL backend on AWS Lambda behind API Gateway, storing playlists in S3 and calling The LastFM API; functions are tiny (39, 36, 49 lines in the demo), deployed with a DPL/npm script, billed per 100ms with 100 concurrent executions by default and a 1 million free-requests tier, versioned for CI, monitored via CloudWatch, and the end-to-end jukebox demo deploys and works while advising to avoid more than three Lambda hops to limit latency.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:12What Is Lambda
- 4:44The Api Gateway
- 6:29Graph ql Server as a Lambda Function
- 12:41Create the Endpoint on the Api Gateway
- 13:59Enable Cross-Origin Requests
- 15:03Front End
- 17:48Graphic Ql
- 20:35How To Tame Your Micro-Services
- 21:05Architecture Diagrams
related talks
54mServerless Architectures: no servers allowed!
51mServerless - a backend thing that gives superpowers to frontend developers
40mThe serverless startup
44mServerless: Giving superpowers to frontend developers
29mDeploying GraphQL in a Serverless Context
47mServerless Microservices
49mLIFE: Serverless Architectures for True Hipsters
54mServerless beyond Functions