My team switched with AWS lambda and it was convenient. I definitely recommend using a framework like the Serverless framework. One benefit of the framework is

My team switched with AWS lambda and it was convenient. I definitely recommend using a framework like the Serverless framework. One benefit of the framework is that it supports multiple vendors so you don’t have to port cloudformation templates over, but it also supports a ton of plugins that make development easy. Our team had nearly zero scaling issues and our costs were lower than any other team in our org who were using ECS or EC2. An example of an issue was that a service I wrote was timing out for certain parameters and I had to increase the memory from the lowest memory setting so it could finish in time. But those kinds of things were rare. It was a Flask app and if needed we could have easily set up a docker container and thrown it in EC2 or ECS but we never needed to. Cold starts were annoying but mostly solved with provisioned concurrency which can be autoscaled. It was sometimes annoying to not be able to log into a production host and debug something but I guess it’s not good to do that anyway. Overall I’d recommend going serverless if you don’t know what your load is going to be or know it’s going to scale up slowly. If you know it’s worth the cost of ECS/EC2 from the start, it’s computationally intensive or requires a lot of RAM, then just go with ECS/EC2 (or EKS).