Комментарии:
🔴 - To support my channel, I’d like to offer Mentorship/On-the-Job Support/Consulting ([email protected])
ОтветитьI think this experimentation demonstrate how fast nodejs platform vs golang binary gets executed in lambda, or may be how fast the corresponding runtime gets loaded; because, both downloading file and saving to DB is IO operation.
To be fair, you also need to add some comparison of CPU load, say math, data processing, etc ops performance comparison as well to get he full picture.
guys you need to take care that Nodejs scales better on cloud functions then go lang! Go lang has much longer cold start then nodejs. We run 20k req/s and nodejs was cheaper at the end
ОтветитьGreat aws lambda performance research. Would interesting to compare just calculation perfprmance
ОтветитьWhy exactly is Go faster here? Because I know that NodeJS is actually significantly faster at some types of code (due to JIT).
ОтветитьTotal time's where within a second of each other though?
ОтветитьHad been learning express JS and i still don't want to say this but , Go rocks !
ОтветитьBetter to test Bun or Deno against Golang as Node is inferior in the JS world now.
Ответитьu from russia, dude?)
your wery cleary pronuorce words, is a good for me
really, i can understand your speak, but i from russia
btw, this message i writed nearly without transaltor
maybe my english language lvl upped..
maybe this messages contain errors, i not good know this lang
@Anton Putra could you do a Go vs c# aws Lambda ?
ОтветитьGraalVM?
ОтветитьLove your videos and how you don't type live and only explain what's essential. Thanks 💯
Ответитьлэт ми сэй фром май харт сэнькЪ ю фор зис интерестинг видео 🤡
ОтветитьПоработай над акцентом. Русский акцент хуже индусского.
ОтветитьCould you please test java and PHP also?
ОтветитьThanks, cool comparison. But I would compare 99 percentile. And the difference a bit less - 22%. Sure that Go is much faster, but a lot of time both routines are slowed by IO operations
ОтветитьNice video. Given the intro, I was hoping this video would actually run these for a while and compare the real AWS costs of each. Then end the video with how much money/day is actually saved
ОтветитьIt seems that you are using the full aws sdk for node js which is like a 75 mbs library. This can be tried by using the latest aws sdk which allows using only the packages for S3 and Dynamodb. Although, I am not fully sure if reducing this size will have a as great impact on the performance since the lambda containers will be reused for many requests.
ОтветитьOne video on Node vs C#.
ОтветитьPlease php vs nodejs
ОтветитьDo more such comparison videos with Node and Go with different use cases
Much appreciated
Thanks, please compare rust and go
ОтветитьI think what go is a waste of time, i prefer learn Rust instead, more performance, same ugly sintax and more use cases. No one will save my time for me
ОтветитьThe Go code would have been much faster if you would have implemented the downloadImage function as a gorutine. Correct me if I am wrong thou.
ОтветитьWhat about Java Quarkus ?
Ответитьvar?!
ОтветитьI know that majority of people never considered C# as a real competitor for nodejs/go/python in lambdas but I have to say that today it worth to try. In .Net 6 there is ahead of time compilation and it helps to solve cold start issue. According to the my test it is on the same level as nodejs with 2Gb of RAM. But C# project is much easier to develop and support in the long terms.
ОтветитьGreat video!! So real!!
ОтветитьNot by a wide margin, considering go is compiled.
ОтветитьStraight to the point! Thank you!!
ОтветитьGo is a great language for back end
ОтветитьGood comparison video! Just wondered, Is there any reason to change regacy node app to go language application??
ОтветитьDoes this also reflect cold start time?
ОтветитьIn AWS lambda downloads you
ОтветитьTest Bun vs Go... :-)
ОтветитьWould be interesting to test with the modular v3 node sdk, should reduce startup by a bit.
ОтветитьQuick and to the point! Thanks!
ОтветитьNPM, which stands for NPM Package Manager, with NPM standing for NPM Package Manager, with NPM standing for NPM Package Manager, with NPM standing for NPM Package Manager, with NPM standing for NPM Package Manager, with NPM standing for NPM Package Manager, with NPM standing for NPM Package Manager, with NPM standing for NPM Package Manager, with NPM standing for NPM Package Manager, with NPM standing for NPM Package Manager, with NPM standing for NPM Package Manager, with NPM standing for NPM Package Manager, with NPM standing for NPM Package Manager...
ОтветитьNice video Anton! Do you think AWS Lambda runtime has a big impact here? I mean, would we be able to infer this results doing the same benchmarks locally?
ОтветитьThank you, Anton. Is there any chance to add python for comparison?
Ответить