I use https://github.com/rimutaka/lambda-debug-proxy to run Lambdas locally while still being part of the AWS pipeline. It eliminates the need to emulate the input/output. That tool is for Rust only, but there is no reason why it can't be ported to other languages.
This is like a drunk ex bursting into your apartment, smashing furniture and demanding that you stop seeing that new boyfriend. Not a winning strategy by any means.
The articles states that it takes approximately 1000 requests to optimize / warm up. I suspect that they had concurrency set at the default 999, so the first 999 requests would spin up new instances.
Does that mean their 15,000 requests were actually 15 requests spread over 1000 instances?
I would love to see their pitch deck with the TAM and that sweet x10000 ROI with their 10% fee! :)
Although they may add value to OSS in the short term by bringing in the $$$ we wouldn't otherwise get, their ultimate purpose as a business is to maximize the return to the shareholders, who are not you or me.
What we really need is more competition in this space to drive the fees down.
Andrew, it would be interesting to hear a bit about the founding story. One question I'd like to ask is how did you acquire the customers in the early days? What was the plan for that and what actually worked?