lambdaws

Deploy, run and get results from Amazon AWS Lambda in a breeze

4Distinct people

4Mentions

0Explicit recommenders

1.3KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

Deploy, run and get results from Amazon AWS Lambda in a breeze

GitHub

No documented product use has been verified yet.

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

No other repository is repeatedly linked in the same discussions.

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

HN mentions by 3-hour interval4 dated mentions

Observed mentions: 2015-01-13 04:04:06 UTC to 2015-01-15 20:34:16 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
Jan 13, 03:00	2015-01-13 03:00:00 UTC	2015-01-13 06:00:00 UTC	1	1	0
Jan 13, 06:00	2015-01-13 06:00:00 UTC	2015-01-13 09:00:00 UTC	2	0	2
Jan 13, 09:00	2015-01-13 09:00:00 UTC	2015-01-13 12:00:00 UTC	0	0	0
Jan 13, 12:00	2015-01-13 12:00:00 UTC	2015-01-13 15:00:00 UTC	0	0	0
Jan 13, 15:00	2015-01-13 15:00:00 UTC	2015-01-13 18:00:00 UTC	0	0	0
Jan 13, 18:00	2015-01-13 18:00:00 UTC	2015-01-13 21:00:00 UTC	0	0	0
Jan 13, 21:00	2015-01-13 21:00:00 UTC	2015-01-14 00:00:00 UTC	0	0	0
Jan 14, 00:00	2015-01-14 00:00:00 UTC	2015-01-14 03:00:00 UTC	0	0	0
Jan 14, 03:00	2015-01-14 03:00:00 UTC	2015-01-14 06:00:00 UTC	0	0	0
Jan 14, 06:00	2015-01-14 06:00:00 UTC	2015-01-14 09:00:00 UTC	0	0	0
Jan 14, 09:00	2015-01-14 09:00:00 UTC	2015-01-14 12:00:00 UTC	0	0	0
Jan 14, 12:00	2015-01-14 12:00:00 UTC	2015-01-14 15:00:00 UTC	0	0	0
Jan 14, 15:00	2015-01-14 15:00:00 UTC	2015-01-14 18:00:00 UTC	0	0	0
Jan 14, 18:00	2015-01-14 18:00:00 UTC	2015-01-14 21:00:00 UTC	0	0	0
Jan 14, 21:00	2015-01-14 21:00:00 UTC	2015-01-15 00:00:00 UTC	0	0	0
Jan 15, 00:00	2015-01-15 00:00:00 UTC	2015-01-15 03:00:00 UTC	0	0	0
Jan 15, 03:00	2015-01-15 03:00:00 UTC	2015-01-15 06:00:00 UTC	0	0	0
Jan 15, 06:00	2015-01-15 06:00:00 UTC	2015-01-15 09:00:00 UTC	0	0	0
Jan 15, 09:00	2015-01-15 09:00:00 UTC	2015-01-15 12:00:00 UTC	0	0	0
Jan 15, 12:00	2015-01-15 12:00:00 UTC	2015-01-15 15:00:00 UTC	0	0	0
Jan 15, 15:00	2015-01-15 15:00:00 UTC	2015-01-15 18:00:00 UTC	0	0	0
Jan 15, 18:00	2015-01-15 18:00:00 UTC	2015-01-15 21:00:00 UTC	1	1	0

4 sources

It looks like SQS is only used for the out-of-band return path. The execution is triggered with the AWS SDK's invoke async option: https://github.com/mentum/lambdaws/blob/master/lib/LambdaHel... Documentation on this option: http://docs.aws.amazon.com/lambda/latest/dg/walkthrough-cust...

MMh. Using toString to serialize a JS function breaks for some functions doesn't it: https://github.com/mentum/lambdaws/blob/master/lib/LambdaHel... It seems here is a discussion about the topic: http://perfectionkills.com/state-of-function-decompilation-i...