You may not realise that you can write AWS Lambda functions in a recursive manner to perform long-running tasks. Here’s two tips to help you do it right. AWS Lambda limits the maximum execution time of a single invocation to 5 minutes. Whilst this limit might be raised in the future, it’s likely that you’ll still …
Write recursive AWS Lambda functions the right way Read More »
Threats to the security of our serverless applications take many forms, some are the same old foes we have faced before; some are new; and some have taken on new forms in the serverless world. As we adopt the serverless paradigm for building cloud-hosted applications, we delegate even more of the operational responsibilities to our …
One of the complaints developers often have for AWS Lambda is the inability to run and debug functions locally. For Node.js at least, the Serverless framework and VS Code provides a good solution for doing just that. An often underused feature of the Serverless framework is the invoke local command, which runs your code locally by …
Hi everyone, just a quick note to let you know that I’m running a live online course with O’Reilly on designing serverless architectures with AWS Lambda. It’s a 2-day course on September 11-12th with 6 hours in total, and it’s available for free if you have a subscription with SafariBooksOnline. Registration for the course is open till September …
I’m running a live course on designing serverless architecture with AWS Lambda Read More »
Security in serverless world from Yan Cui
The Saga pattern is a pattern for managing failures, where each action has a compensating action for rollback. In Hector Garcia-Molina’s 1987 paper, it is described as an approach to handling system failures in a long-running transactions. It has become increasingly relevant in the world of microservices as application logic often needs to transact across …
Applying the Saga pattern with AWS Lambda and Step Functions Read More »
part 1: overview part 2: testing and CI/CD part 3: ops part 4: building a scalable notification system part 5: building a better recommendation system <- you’re here When I joined Yubl in April 2016, it had launched just 2 months earlier, after a long and chaotic development cycle that lasted more than 2 years …
AWS announced general availability of AWS Lambda support for AWS X-Ray back in May. It’s taken me a while to try it out, and whilst I see plenty of values I think its current limitations significantly restricts its usefulness in a complex system. I found Lambda-specific documentations to be fragmented and I had to rely …
aws x-ray and lambda : the good, the bad and the ugly Read More »
In the last post I compared the coldstart time for Lambda functions with different language, memory and code size. One of the things I learnt was that idle functions are no longer terminated after 5 minutes of inactivity. /2017/06/aws-lambda-compare-coldstart-time-with-different-languages-memory-and-code-sizes/ It is a fantastic news and something that Amazon has quietly changed behind the scene. However, …
Finding coldstarts : how long does AWS Lambda keep your idle functions around? Read More »
A while back we looked at the performance difference between the language runtimes AWS Lambda supports natively. We intentionally omitted coldstart time from that experiment as we were interested in performance differences when a function is “warm”. However, coldstart is still an important performance consideration, so let’s take a closer look with some experiments designed …
aws lambda – compare coldstart time with different languages, memory and code sizes Read More »
By continuing to use the site, you agree to the use of cookies. more information
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.