4 ms·
There are a few differences: * CGI is the closest UNIX thing you can find, fork a process, write on STDIN, read from STDOUT. Lambda actually is a framework for
by rakoo 11y ago
There are a few differences:
* CGI is the closest UNIX thing you can find, fork a process, write on STDIN, read from STDOUT. Lambda actually is a framework for running javascript/java/python code, from which you can call actual binaries.
* Lambda's attractive point is that containers are reused, which means that instead of paying the full price of a new process your context is already "hot", even for the actual binary you run. That means less latency and less CPU usage, allowing you to scale far more easily
I'm no Lambda user so I'm possibly wrong, but the idea and execution behind sure looks nice.
- toomuchtodo 11y agoBoth your statements are correct: Amazon is most likely running lxc containers under the hood though, so anyone could duplicate what Lambda does using an evaluator for javascript/python/etc with a REST API containerized in a docker container. Disclaimer: I am a heavy Lambda user.
- Eridrus 11y agoI haven't done my own experiments, but reading the Lambda docs on Security has made me think these are real VMs and not containers.