That really depends on the size of your app. You also lose the ability to run debuggers. Not to mention how hard is to run serverless java applications, which is the dominant enterprise programming language.
Don't take me wrong, I am a big fun of serverless. We use it in production too. But I also think it does not cover a large percentage of the deployment spectrum, at least for a few years. And serverless can also benefit from tools like Okteto
Docker setup that allows me to test my functions locally - I have a wrapper that simulates the handoff between AWS ALB and AWS Lambda.
When ready, I merge into master, push, and they deploy to AWS through CI - I have simple Python scripts that manage Lambda Layer creation, environment variable configuration, etc.
Right, that works. I think that setup does not scale well for large teams or if you are not able to run all your services locally due to resource constraints
Serverless Framework deploys are now less than three seconds. It's almost exactly like `run watch` now!
I deploy to a dev AWS account, then a staging AWS account, and then promote to prod out of github.
Check it out: https://github.com/serverless-components/