- Local development is complex. Does one provision a full cloud environment per developer? Emulate a cloud environment locally? These are solvable but it's a grind of special cases.
- Limited customization. Eventually one needs to customize the language / libraries of the lambda. Again these are solvable with a grind of special cases.
- Limited execution model. Not all compute tiers are the same. Some quickly assemble results from a database. Others run for a long time. Others build up a model in RAM before delivering results. Serverless optimizes for some but not all models.
Unlike serverless / lambda, all of the above can be addressed by containers.
- Containers have orchestration solutions for local development and deployment
- Containers are designed to support customization
- Containers can be deployed to run in many different ways.
Not to be a booster, but in my experience containers are the scalable compute architecture.