Webinar: Debugging AWS Lambda Timeouts with Yan Cui

When a Lambda function times out, it’s one of the trickier problems to debug, especially if the function performs multiple IO calls. What was it doing when it timed out? And how do I identify these timeout errors quickly when Lambda lumps them together with other unhandled exceptions? In this webinar, we will show you how to identify and debug timeout errors, and strategies for mitigating timeouts and degraded performance more gracefully when there are underlying issues.

Webinar: Debugging Slow Lambda Response Times

One of the most common performance issues in serverless architectures is elevated latencies from external services, such as DynamoDB, ElasticSearch, or Stripe. In this webinar, we will show you how to quickly identify and debug these problems, and some best practices for dealing with poor performing 3rd party services. Here are some of the topics we cover.

Webinar: Improving AWS Lambda Cold Starts

AWS has improved Lambda cold starts by leaps and bounds in the last year. But for performance-sensitive applications such as user-facing APIs, Lambda cold starts are still a thorn in one’s side, especially when working with languages such as Java and .Net Core. In this webinar, we will dive into strategies for improving cold start latency and how to mitigate them all together with Provisioned Concurrency, and how Lumigo helps you optimize your use of Provisioned Concurrency.

AWS Lambda Extensions: What are they and why do they matter

There is a growing ecosystem of vendors that are helping AWS customers gain better observability into their serverless applications. All of them have been facing the same struggle: how to collect telemetry data about AWS Lambda functions in a way that’s both performant and cost-efficient. To address this need, Amazon is announcing today the release of AWS Lambda Extensions.


This is all you need to know about Lambda cold starts

So much has been written about Lambda cold starts. It’s easily one of the most talked-about and yet, misunderstood topics when it comes to Lambda. Depending on who you talk to, you will likely get different advice on how best to reduce cold starts. So in this post, I will share with you everything I have learned about cold starts in the last few years and back it up with some data.


How to Debug Slow Lambda Response Times

When you build your application on top of Lambda, AWS automatically scales the number of “workers” (think containers) running your code based on traffic. And by default, your functions are deployed to three Availability Zones (AZs). This gives you a lot of scalability and redundancy out of the box. When it comes to API functions, every user request is processed by a separate worker. So the API-level concurrency is now handled by the platform.


What alerts should you have for serverless applications?

A key metric for measuring how well you handle system outages is the Mean Time To Recovery or MTTR. It’s basically the time it takes you to restore the system to working conditions. The shorter the MTTR, the faster problems are resolved and the less impact your users would experience and hopefully the more likely they will continue to use your product! And the first step to resolve any problem is to know that you have a problem.


Debugging AWS Lambda Timeouts

Some time ago, an ex-colleague of mine at DAZN received an alert through PagerDuty. There was a spike in error rate for one of the Lambda functions his team looks after. He jumped onto the AWS console right away and confirmed that there was indeed a problem. The next logical step was to check the logs to see what the problem was. But he found nothing. And so began an hour-long ghost hunt to find clues as to what was failing and why there were no error messages.