TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Debugging Lambdas by re-materializing execution contexts on your local machine

6 pointsby estebanloralmost 8 years ago

1 comment

ben-comanalmost 8 years ago
A bit of context from the original community mail list post, &quot;it supports post mortem debugging by saving a zipped execution context onto S3. This is particularly satisfying as at a recent serverless conference (JeffConf) there was a panel where poor development tools on serverless platforms was highlighted as a real problem.<p>Debugging something short lived like a Lambda execution is quite startling, as the current answer is &#x27;add more logging&#x27;, and we all know that sucks. To this end, I’ve created a little screencast showing this in action - and it was pretty cool because it was a real example I encountered when I got everything working and was trying my test application out.&quot;<p>@2:17 &quot;PharoLambda has serialized the execution context of its application and saved it into [my S3 bucket] ... [then on my local machine] rematerializes a debugger [on that context].&quot;