99 Problems But a Container Ain’t One: Forget Serverless, Let’s Talk Containerless Development
summary
Argues that Cloud Foundry’s CF push model plus buildpacks lets most apps migrate far easier than moving to functions-only serverless, and that containers should be hidden not surfaced. Describes tradeoffs between Docker images and droplets, ties everything to stateless design, and reports a hack‑day prototype that binds events to pushed apps (FMap) which scales instances up and down and successfully processes queued messages. Claims the future is Containerless developer UX.
AI-written summary · about
chapters (9)
- 0:00Introduction and overview
- 2:13Simplicity and abstractions
- 5:24Containers vs simplicity
- 7:34Serverless and state
- 9:00Stateless apps and scaling
- 12:31Services and pushing limits
- 13:57Good vs bad problems
- 14:46Containerless manifesto
- 15:48Unified UX and demo
related talks
31mFunction to Container - Building a FaaS Experience
51mWho needs containers in a serverless world?
24mContainers vs Serverless from a DevOps standpoint
35mContainer vs. Serverless: The Good, the Bad and the Ugly
44mServerless and containers are coming together: an AWS perspective
01h 00mMicroservices and Serverless
11mKeynote: Containerful Serverless
55mSpring, Functions, Serverless and You
