Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 01 2019 16:35
    praveenvelampudi7 commented #49
  • May 29 2018 19:21
    contractorwolf commented #49
  • May 10 2018 02:55
    deoresheetal commented #49
  • Sep 27 2017 13:25
    contractorwolf unassigned #49
  • Sep 27 2017 13:25
    contractorwolf commented #49
  • May 12 2017 15:22

    EFF on master

    Update README.md (compare)

  • May 12 2017 15:21
    EFF closed #70
  • May 12 2017 15:21
    EFF commented #70
  • May 11 2017 00:04
    Echelonsecretintelligenceofficer commented #70
  • Feb 13 2016 03:45
    vboctor opened #70
  • Jan 13 2016 18:31

    EFF on master

    Update README.md (compare)

  • Dec 11 2015 22:00
    adelevie opened #69
  • Oct 23 2015 15:55
    EFF commented #68
  • Oct 16 2015 18:31
    jakelodwick opened #68
  • Oct 06 2015 15:52
    oortlieb commented #67
  • Oct 06 2015 15:47
    slvnperron commented #67
  • Oct 06 2015 15:34
    oortlieb opened #67
  • Oct 01 2015 04:45
    chrxn commented #66
  • Sep 29 2015 17:00

    slvnperron on master

    Added 'logs:*' as a required pe… Merge pull request #66 from chr… (compare)

  • Sep 29 2015 17:00
    slvnperron closed #66
Austen
@ac360
@etnbrd I'd love to see simple web service components as lambdas
What are you thinking about building?
Etienne Brodu
@etnbrd
I am currently doing my PhD on a compiler from node.js to what seems to be pretty similar to lambdas.
Austen
@ac360
Interesting
Etienne Brodu
@etnbrd
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
You mean onto many lambdas?
Etienne Brodu
@etnbrd
Exactly.
Austen
@ac360
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
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
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
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
Right
I'm going to bed. Good luck etnbrd!
Etienne Brodu
@etnbrd
Thanks :)
Good night, then :)
EFF
@EFF
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.
EFF
@EFF
Hey @etnbrd I'll look up your project for sure ! looks interesting !
Etienne Brodu
@etnbrd
@EFF, this is a good place to start : https://github.com/etnbrd/flx-poster
EFF
@EFF
@etnbrd Great thanks !
Austen
@ac360
Does anyone know how long it takes to receive an invite to AWS Lambda Preview?
Sylvain Perron
@slvnperron
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
Hi slvperron Thanks for the tip and the lambdaws project is super cool, nice work
Sylvain Perron
@slvnperron
Thanks @ac360 glad you like it !!
Austen
@ac360
Apparently, I'm not the only one!
Sylvain Perron
@slvnperron
it gained huge traction today hehe
Austen
@ac360
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
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
Right, Ok. Those rough numbers are helpful.
Sylvain Perron
@slvnperron
We are looking forward the 2s to go away. This will make function calls very fast
Austen
@ac360
Yes, I wonder why AWS does that.
Sylvain Perron
@slvnperron
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
Hmm, it could seem like that's in place to discourage certain behavior
Anyway, super cool project. Very clever.
Sylvain Perron
@slvnperron
:)
Austen
@ac360
I'll be watching it. Good luck to you!
EFF
@EFF
@ac360 hope you get access soon so you can step in and contribute ;)
Austen
@ac360
@EFF Yep, I can't wait to take it for a test run