3 ms·
The real question here is still: why doesn't Amazon offer a GET interface to Lambda? It's so, so, so close. So almost. They offer POST (through a work-around wi
by nothrabannosir 11y ago
The real question here is still: why doesn't Amazon offer a GET interface to Lambda? It's so, so, so close. So almost. They offer POST (through a work-around with S3), why not GET?
That is the real destination. With lambda serving GETs, we can remove the "for a single page app" from the title. AWS is so close to fulfilling the promise of its cloud: let developers worry about code.
- ryeguy 11y agoSince lamba is already handling the backend api calls, couldn't you just host the html and js in s3/cloudfront and not have to host anything?
- justincormack 11y agoIt is a bit slow still. Jitsu[1], which starts unikernels is fast enough to do per request image booting, but Amazon seem to have a 1s cold start which is just a bit slow. [1] https://github.com/mirage/jitsu https://github.com/mirage/jitsu
- fwefwefwef 11y agoAh, so there is a 1s cold start. I couldn't understand how they managed to get a container (which I imagine they are using?) running "within milliseconds". I guess the millisecond claim only holds for concurrent requests then?
- justincormack 11y agoSeems so for the measurements I have seen yes. Concurrent or close before it has been shut down.
- NeutronBoy 11y agoThis is the one thing I need to make them useful! This would make Lambda's so much easier to invoke, without needing to build custom code to put together an SQS message or similar.