Hello, the slides and recording of my talk — The present and future of Serverless observability — at ServerlessConf Paris is now available. Enjoy! :-) The present and future of Serverless observability from Yan Cui
Hello, the slides and recording of my talk – Serverless Design Patterns – at the London Dev Community is now available. Enjoy! :-) Serverless Design Patterns (London Dev Community) from Yan Cui
After my post on monolithic functions vs single-purposed functions, a few people asked me about the effect monolithic functions have on cold starts, so I thought I’d share my thoughts here. The question goes something like this: Monolithic functions are invoked more frequently so they are less likely to be in cold state, while single-purposed …
AWS Lambda – monolithic functions won’t help you with cold starts Read More »
This is a the first in a mini series that accompanies my “the present and future of Serverless observability” talk at ServerlessConf Paris and QCon London. part 1 : new challenges to observability <- you’re here part 2 : first party observability tools from AWS part 3 : 3rd party observability tools part 4 : the future of Serverless observability 2017 …
Serverless observability brings new challenges to current practices Read More »
In the last post I discussed the pros & cons of following the Single Responsibility Principle (SRP) when moving to the serverless paradigm. One of the questions that popped up on both Twitter and Medium is “how do you deal with shared code?”. It is a FAQ whenever I speak at user groups or conferences about AWS Lambda, alongside “how do …
AWS Lambda – how best to manage shared code and shared infrastructure Read More »
A funny moment (at 38:50) happened during Tim Bray’s session (SRV306) at re:invent 2017, when he asked the audience if we should have many simple, single-purposed functions, or fewer monolithic functions, and the room was pretty much split in half. Having been brought up on the SOLID principles, and especially the single responsibility principle (SRP), …
AWS Lambda – should you have few monolithic functions or many single-purposed functions? Read More »
This is a lesson that I wished I learnt when I first started using AWS Lambda in anger, it would have made my life simpler right from the start. But, we did get there before long, and it allowed us to track and include correlation IDs in our log messages (which are then pushed to an ELK stack)which would …
You need to use structured logging with AWS Lambda Read More »
When I discuss AWS Lambda cold starts with folks in the context of API Gateway, I often get responses along the line of: Meh, it’s only the first request right? So what if one request is slow, the next million requests would be fast. Unfortunately that is an oversimplification of what happens. Cold start happens once for …
I’m afraid you’re thinking about AWS Lambda cold starts all wrong Read More »
With API Gateway and Lambda, you’re forced to use relatively short timeouts on the server-side: API Gateway have a 30s max timeout on all integration points Serverless framework uses a default of 6s for AWS Lambda functions However, as you have limited influence over a Lambda function’s cold start time and have no control over the amount of …
AWS Lambda – use the invocation context to better handle slow HTTP responses Read More »
This is part 2 of a multipart series that explores ideas on how we could apply the principles of chaos engineering to serverless architectures built around Lambda functions. part 1: how can we apply principles of chaos engineering to Lambda? part 2: latency injection for APIs <- you’re here part 3: fault injection for Lambda …
Applying principles of chaos engineering to AWS Lambda with latency injection 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.