These are chat archives for mentum/lambdaws

13th
Jan 2015
Max Bittker
@MaxBittker
Jan 13 2015 05:09
You can't use this client side, correct? due to the fact you'd be publishing your aws key?
Christian Bundy
@christianbundy
Jan 13 2015 06:16
You can upload a server-side application that responds to HTTP requests (and therefore creates a client-side application), but no – you can't only deploy a client-side app. @MaxBittker
Etienne Brodu
@etnbrd
Jan 13 2015 09:33
Hello :)
Would you, guys, be interested in a compiler from vanilla node.js to lambdaws ?
That is transforming a full node.js application into many lambdaws.
Austen
@ac360
Jan 13 2015 09:36
etnbrd Doesn't AWS Lambda already have Node.js support built in?
Etienne Brodu
@etnbrd
Jan 13 2015 09:38
Yes, but isn't there any limit on the size of a lambda ?
I mean, is it possible to upload a full web service as a lambda ?
Or would it be more efficient to slice it into many different lambdas ?
Austen
@ac360
Jan 13 2015 09:38
I think there is a limit of 500mb
Which is a lot
Etienne Brodu
@etnbrd
Jan 13 2015 09:39
Yes, actually :p
Austen
@ac360
Jan 13 2015 09:39
@etnbrd I'd love to see simple web service components as lambdas
What are you thinking about building?
Etienne Brodu
@etnbrd
Jan 13 2015 09:40
I am currently doing my PhD on a compiler from node.js to what seems to be pretty similar to lambdas.
Austen
@ac360
Jan 13 2015 09:41
Interesting
Etienne Brodu
@etnbrd
Jan 13 2015 09:41
Instead of deploying a full node.js application to one server, the compiler slice it, for the application to be deployable onto many servers.
It is basically breaking the scalability limit of a single machine imposed by the node.js event loop.
Austen
@ac360
Jan 13 2015 09:42
You mean onto many lambdas?
Etienne Brodu
@etnbrd
Jan 13 2015 09:42
Exactly.
Austen
@ac360
Jan 13 2015 09:42
Right
I'm not part of this project. I just discovered it today, like most, and I love the technology.
But that sounds like it would have serious use.
Etienne Brodu
@etnbrd
Jan 13 2015 09:42
Thanks for the support :)
Anyway, If you are interested in this compiler I am talking about, you can look on my flx-* repositories.
I didn't actually used lambdas, but I called them fluxions.
for the contraction between flux and function.
Austen
@ac360
Jan 13 2015 09:45
Ok, I'll put it in my notes
It's almost 2am here in California and I'm about to go to sleep :)
Etienne Brodu
@etnbrd
Jan 13 2015 09:45
The only difference I can see is that fluxions are statefull, while lambdas are stateless, but it is a minor difference that can be resolved with a third party persistent storage.
Ok :p
Austen
@ac360
Jan 13 2015 09:46
Right
I'm going to bed. Good luck etnbrd!
Etienne Brodu
@etnbrd
Jan 13 2015 09:46
Thanks :)
Good night, then :)
Damn sorry guys for the lack of answers, I guess we are not in the same timezone ;) @MaxBittker supporting client side requests is on our road map, we'll try to focus our efforts on that.
Hey @etnbrd I'll look up your project for sure ! looks interesting !
Etienne Brodu
@etnbrd
Jan 13 2015 13:22
@EFF, this is a good place to start : https://github.com/etnbrd/flx-poster
@etnbrd Great thanks !
Austen
@ac360
Jan 13 2015 18:04
Does anyone know how long it takes to receive an invite to AWS Lambda Preview?
Sylvain Perron
@slvnperron
Jan 13 2015 18:05
They send out invites by batch every few days
you can probably contact them directly on the AWS forum so it goes faster
Austen
@ac360
Jan 13 2015 18:06
Hi slvperron Thanks for the tip and the lambdaws project is super cool, nice work
Sylvain Perron
@slvnperron
Jan 13 2015 18:06
Thanks @ac360 glad you like it !!
Austen
@ac360
Jan 13 2015 18:06
Apparently, I'm not the only one!
Sylvain Perron
@slvnperron
Jan 13 2015 18:07
it gained huge traction today hehe
Austen
@ac360
Jan 13 2015 18:07
I'm curious if you have any benchmarks of how long it takes to run the simple calculator function example in the documentation.
Especially on the first run, when the zip file is being uploaded
Sylvain Perron
@slvnperron
Jan 13 2015 18:09
Yes. There’s an extra 2000ms due to an issue on AWS Lambda side. We are working with AWS team to resolve this. They basically added a sleep but it shouldn’t be there.. there’s also an additionnal ~100ms overhead from using Lambdaws (SQS push etc). Otherwise it’s the real time of the function
On the first run it will take at least 3s before Lambdaws picks up the zip file and process it. But that’s just on upload (I assume you don’t re-upload it every time)
Austen
@ac360
Jan 13 2015 18:10
Right, Ok. Those rough numbers are helpful.
Sylvain Perron
@slvnperron
Jan 13 2015 18:10
We are looking forward the 2s to go away. This will make function calls very fast
Austen
@ac360
Jan 13 2015 18:11
Yes, I wonder why AWS does that.
Sylvain Perron
@slvnperron
Jan 13 2015 18:11
I think they need it when you push an object on S3 for propagation reasons
but it shouldn’t be the case when you invoke it directly like we do
Austen
@ac360
Jan 13 2015 18:12
Hmm, it could seem like that's in place to discourage certain behavior
Anyway, super cool project. Very clever.
Sylvain Perron
@slvnperron
Jan 13 2015 18:12
:)
Austen
@ac360
Jan 13 2015 18:12
I'll be watching it. Good luck to you!
@ac360 hope you get access soon so you can step in and contribute ;)
Austen
@ac360
Jan 13 2015 18:33
@EFF Yep, I can't wait to take it for a test run
I'm most interested in building a series of open-source lambda functions for common utilities
We had a similar idea, would be awesome !
Austen
@ac360
Jan 13 2015 18:37
Each would be bundled with the lambdaws project.
Yeah !
It’ll help to find new use cases