News for hackers. Stuff that matters.
Re:AWS Lambda pricing now per ms by koolba on Tuesday December 01, 2020 @12:54PM (#25267714)
And you can pick any language you'd like as it supports arbitrary containers now too: https://news.ycombinator.com/item?id=25267182
Re:AWS Lambda pricing now per ms by freeqaz on Tuesday December 01, 2020 @02:12PM (#25268656)
This should be at the top of this thread! This is huge and fixes my #1 gripe with Lambda -- that managing dependencies is "non-standard" and you can't use tools like Docker. Plus, the 250MB limit is brutal.

This is really, really exciting!

Re:AWS Lambda pricing now per ms by adwww on Tuesday December 01, 2020 @02:33PM (#25268878)
Oh that's quite big news if you run an app that has to be deployed cross cloud.

We use very little serverless at the moment, because the three clouds we need to deploy to have infuriating differences between their execution and deployment environments. Eg. How they manage dependancies, the runtimes, how you describe and deploy each function.

Compared at least to K8 where the containers you build run just fine wherever you put them.

Re:AWS Lambda pricing now per ms by throwaway894345 on Tuesday December 01, 2020 @01:25PM (#25268072)
Wow, I haven’t read yet, but I’m very curious if this affects the size limits on the lambdas. I’ve tried to build lambdas for a small Python use case, but by the time I imported pandas and a few other libraries I exceeded the 250 mb limit and migrated to ECS/Fargate, but the startup times were much longer.
Re:AWS Lambda pricing now per ms by fitzoh on Tuesday December 01, 2020 @01:51PM (#25268434)
https://twitter.com/chrismunns/status/1333825503464214530

Docker containers can be up to 10gb, traditional lambdas are still limited to 250mb.

Re:AWS Lambda pricing now per ms by munns on Tuesday December 01, 2020 @01:55PM (#25268476)
Thats me. We've got some fun things we do behind the scenes to keep Lambda container image support snappy. SO yes, up to 10gb artifacts with container image support.
[dead]
Re:AWS Lambda pricing now per ms by throwaway894345 on Tuesday December 01, 2020 @03:51PM (#25269728)
I don’t know how this is related to my comment. In my case we used a slow language (although Python’s poor performance and its large bundle sizes are only indirectly related at best) and we had to spend a lot more by moving to ECS/Fargate. If we were using Go, our bundle sizes would’ve been 30x smaller (I checked) and would’ve fit in a lambda easily. Not only would it have fit easily, it would have made a lot of progress before the Python version even finished importing its dependencies. And in top of all of that, it would have out-performed the Python version by a good order of magnitude. If anything, my anecdote supports the idea that Amazon wants you to use fast languages, especially now that they offer per-ms pricing for lambdas.
Re:AWS Lambda pricing now per ms by endgame on Tuesday December 01, 2020 @11:03PM (#25273119)
The thing you put inside the container still has to speak Lambda's API, but yes, pretty cool.
Re:AWS Lambda pricing now per ms by bdcravens on Tuesday December 01, 2020 @01:19PM (#25268007)
For per ms billing to matter, you probably want to limit your language choices.