3 ms·
You can't. Are you actually asking this question? Or you pretending to ask a question because you think the fact that AWS Lambda run on AWS is some huge gotch
by nuclearnice3 5y ago
You can't.
Are you actually asking this question?
Or you pretending to ask a question because you think the fact that AWS Lambda run on AWS is some huge gotcha that I never imagined and no one would ever tolerate?
I explicitly note vendor-specific baggage. AWS revenue is over 45 billion annually and half of customers use lambda.
- throwaway3699 5y agoMy point is that the industry really hasn't moved on from the old LAMP stack if it's been replaced by a single company. When it truly comes down to it, the day-to-day tools are not ours if they aren't open. And if deploying a lambda function on my own hardware is vastly more complex, then the tools haven't really changed, they just got outsourced. There are a bunch of semi-standards like Serverless Framework and Knative, but nothing concrete.
- nuclearnice3 5y agoI agree the tools got outsourced. I also agree there are big chunks of LAMP under the covers of running an AWS Lambda. So, in that sense, we haven't "moved on" from the old LAMP stack. I also agree the tools are "not ours" if they aren't open. They do useful things. It's a tradeoff.
- nl 5y ago> And if deploying a lambda function on my own hardware is vastly more complex, then the tools haven't really changed, they just got outsourced. Well... Yeah? I came into web development in 97. Back then almost everything was on shared servers, so pretty much the same thing.