AWS Introducing Provisioned Concurrency for Lambda Functions
1–10 of 74 posts
Re: AWS Introducing Provisioned Concurrency for Lambda Functions
#2As a seasoned AWS developer, I love this feature. However, I wonder how the increasing complexity of AWS affects new devs as they try to grok the offered services. AWS typically does a pretty good job hiding advanced features from beginners, but I wonder how long they can do that.
Re: AWS Introducing Provisioned Concurrency for Lambda Functions
#3So excited for this, between this and the removal of VPC cold start issues recently, avoiding Lambda for APIs because of latency seems to be a thing of the past.
Re: AWS Introducing Provisioned Concurrency for Lambda Functions
#4This is a big deal. Cold starts were always the huge Achilles heal for using lambdas for interactive APIs. Kudos for this.
Re: AWS Introducing Provisioned Concurrency for Lambda Functions
#5Request for anyone on the Lambda team who happens to read this: your API doesn’t appear to offer a way to retrieve the “last modified by” user when grabbing function metadata.
Very unlike other AWS APIs and very annoying.
Re: AWS Introducing Provisioned Concurrency for Lambda Functions
#6Request for anyone on the Lambda team who happens to read this: your API doesn’t appear to offer a way to retrieve the “last modified by” user when grabbing function metadata. Very unlike other AWS APIs and very annoying.
[deleted]
Re: AWS Introducing Provisioned Concurrency for Lambda Functions
#7I am a huge fan of serverless, and AWS as well.
I also find it deeply ironic that their solution to cold starts is to keep the function running 24/7...
Could I include openssh and Apache in my Lambda instance? Maybe run a Minecraft server? :P
Re: AWS Introducing Provisioned Concurrency for Lambda Functions
#8This feels like a step backwards to me, nevermind how necessary it may be. The magic was paying only for what you use on super bursty workloads.
Now this is like throwing your hands up and saying the users bursts are too big for AWS.
Re: AWS Introducing Provisioned Concurrency for Lambda Functions
#9This feels like a step backwards to me, nevermind how necessary it may be. The magic was paying only for what you use on super bursty workloads. Now this is like throwing your hands up and saying the users bursts are too big for AWS.
Lambda’s success was never about bursty workloads, it’s the elastic event driven compute model it enables.
Yes only paying for the compute you actually use is great, but so is having basically limitless compute power (your wallet willing) without the ops overhead and system maintenance.
Cold starts have been a problem fire a while, and while there many be a better way than this long term, ultimately to some degree the solution will always be keeping a function warm. And that’s ultimately compute, and aws is not likely to give that away.
Re: AWS Introducing Provisioned Concurrency for Lambda Functions
#10Request for anyone on the Lambda team who happens to read this: your API doesn’t appear to offer a way to retrieve the “last modified by” user when grabbing function metadata. Very unlike other AWS APIs and very annoying.
Which API specifically are you referring to (GetFuntionConfiguration ?), and which APIs are you comparing it against?