How Serverless Makes Integration TDD a Reality — And Why We Need It
summary
Advocates starting development with integration tests that drive features, then adding unit tests later. Demonstrates building and deploying a full Serverless pipeline on AWS using Lambda, DynamoDB and API Gateway (with queues and parallel Lambda workers), and running the same integration tests against the real cloud infrastructure; notes this scales to large organizations (100+ backend services) while keeping tests stable, though Lambda cold-starts and language trade-offs are practical concerns.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 3:29TDD in real projects
- 7:20Practical task
- 9:25Blockchain basics
- 13:20Integration test start
- 21:44Refactoring and parallel dev
- 23:57Serverless prototyping
- 27:51Miner AWS deployment
- 33:11Scaling with Lambda
- 37:03Unit tests and architecture
- 41:17Integration deployment
- 44:14Summary and benefits
- 47:27When to write tests
- 48:11Q&A
related talks
32mBeyond the Unit: A Holistic Approach to Testing Serverless Architectures
51mTaking Serverless to the Next Level
25mLeveraging Serverless in Full-stack Development
41mYou Don’t Want to Build a Serverless Monolith
09mWorking with Serverless Functions and CI/CD
25mHow Serverless Is Changing the World for Developers
31mAccelerate business innovation with serverless applications
44mServerless Continuous Delivery with the Serverless Framework