News for hackers. Stuff that matters.
Re:Comparing AWS Lambda performance of Node.js, Python, Java... by petethepig on Thursday March 08, 2018 @04:39AM (#16543358)
> This is "AWS Lambda infrastructure for Go is comparable to AWS infra for Java"

I wouldn't even go that far. They are not measuring anything that any real-world application would do. Heck, it's not even a todo app, it's just a "200 OK hello".

It's more like "AWS lambda function invocation overhead for Go is comparable to AWS lambda function invocation overhead for Java".

Re:Comparing AWS Lambda performance of Node.js, Python, Java... by weego on Thursday March 08, 2018 @06:32AM (#16543726)
Sure but if you start adding in language specific Web frameworks / json handling / db work you're no longer testing AWS.

I agree there's questionable value here but at least it's bring constrained to as few variables as possible.

Re:Comparing AWS Lambda performance of Node.js, Python, Java... by lsaferite on Thursday March 08, 2018 @09:02AM (#16544342)
Benchmarking the lambda-add latency is something that is useful as long as it's called out as such a benchmark.