Our company has customers who install our SDK, and that SDK pushes and pulls data from our service. We service ~400 million API calls per month. Half of the ca

Our company has customers who install our SDK, and that SDK pushes and pulls data from our service. We service ~400 million API calls per month. Half of the calls pull static cached data from a CDN (Cloudfront), and the other half ingests data pushed to it from the SDK (anywhere from 10kb to 400kb per call). We run of Elastic Beanstalk, which is basically an abstraction later on top of an autoscaling EC2 cluster. Back when Lambda (and API Gateway) first came out we were excited. It sounded like the perfect way to break free from our “legacy” server architecture. Until you do the pricing calculations. It wasn’t even close. Managed services like Lambda and API Gateway were prohibitively expensive. (Thank god we didn’t begin development with the services before scaling - we would have never been able to scale at those prices). Not only price, but performance was horrible. Lambdas take forever to warm up (unacceptable for latency sensitive use cases). I’ve never really thought of Lambda / API Gateway as anything other than a cool pet toy. Although maybe thats being a little harsh..?