nshap

8 ms·

1.
Why It’s Important to Try and Break Your Serverless Application(blazemeter.com)
1 points by nshap 8y ago|0 comments
2.
AWS Lambda research – billing and timeout mechanism(medium.com)
2 points by nshap 8y ago|0 comments
3.
Interview with serverless apps monitoring startup Epsagon(serverless.zone)
2 points by nshap 8y ago|0 comments
4.
AWS Lambda internals research(medium.com)
2 points by nshap 8y ago|0 comments
5.
AWS Lambda internals research(medium.com)
2 points by nshap 8y ago|0 comments
6.
Distributing messages between AWS services effectively
2 points by nshap 9y ago|0 comments
7.
by nshap 9y ago
Thanks for your the comment. The big majority of serverless users nowadays are on AWS. It might change in the future (probably not), but today the most relevant information regarding latency between serverless functions is due to Lambda and
8.
Distribute messages effectively in serverless applications
2 points by nshap 9y ago|0 comments
9.
Distribute messages effectively in serverless applications(medium.com)
11 points by nshap 9y ago|3 comments
10.
Why your startup needs Serverless Slack bots(medium.com)
2 points by nshap 9y ago|0 comments
11.
Detect unused Lambda functions(medium.com)
2 points by nshap 9y ago|0 comments
12.
The Curse of Dead Lambda Functions(medium.com)
2 points by nshap 9y ago|0 comments
13.
Tired of “dead” Lambda functions?(github.com)
3 points by nshap 9y ago|0 comments
14.
Enumerate Lambda functions across all regions with useful metadata(github.com)
2 points by nshap 9y ago|0 comments