If anyone tells you different you can take stacks like Beanstalk VERY FAR. Probbably way further than you want to. We just moved our highest TPS (Transactions p

If anyone tells you different you can take stacks like Beanstalk VERY FAR. Probbably way further than you want to. We just moved our highest TPS (Transactions per second) and OPS (Objects Per Second) service off of beanstalk after 7 years. At peak this service was serving around 1.1M TPS and around 8M OPS with peaks up to 3M TPS and 14M OPS. It was horizontally scaled and run by about .25 engineers. That was actually the main problem. That and the company got real good at running ECS. Our services are all golang so beanstalk eventually was getting in the way, and one of our last major issues had to do with nginx proxy on bean stalk not keeping up with our go service. There's several other edge cases with Beanstalk like how to do health checks right, and speed of deploys esp when they get wedged. But if you know it you can, as we found, go very far with it, powering a core feature of a very large web property (check my bio). Am I happy we moved off, yes. Was I impressed how big we took a very simple "starter" setup, also yes. Again one of the biggest reasons was that all of our competence in the company was no longer on beanstalk but on ECS where we had solved the issues we had with it with more complex setups more in our control. If I were starting again would I use Beanstalk? no not me personally but when we started ecs didn't exist and beanstalk was better than bare EC2. now I know and am comfortable with ECS. Did it help the company? very much so, we leveraged the heck out of Beanstalk to scale the company horizontally and vertically.