Hi, welcome to another weekly update! It’s been a quiet week, I have been busy finishing off the VPC chapter of my video course Production-Ready Serverless, which should be available to you next week. In the meantime I do have some new posts that I can share with you :-)
We can do better than percentile latencies. I outlined a number of problems with percentile latencies as a latency metric – they are often averaged by providers and that they don’t tell you how bad things are when they go wrong. I proposed some ideas of what we can do instead, including monitoring percentage of requests over SLO instead, and alerting on the absence of successful signal instead of trying to alert on every possible error.
Pricing pitfalls in AWS Lambda. I drilled into the common mistakes people make when it comes to estimating the total cost of their serverless applications. Mistakes such as not considering the 100ms charge blocks, that you’re still paying for idle, and the additional cost of event sources and peripheral services.
With all the media coverage, I don’t think you could have missed the news about the China hardware hack as well as the software side of the hack. Both Amazon and Apple has denied the story, but as a casual observer it just makes it the more believable! As the saying goes “Never believe anything in politics until it has been officially denied.” :-P
Netflix published an awesome post on the design for their edge load balancer, Zuul 2.
Martin Kleppmann’s talk on CRDTs and distributed consistency is finally available on youtube.
Sidney Dekker published a thought provoking article on why we need to better understand “why do things go right?” so we can do more of the right things as much as avoid doing the wrong things.
Jaana Dogan published an equally thought provoking article on Critical Path Driven Development (CPDD), which is a brand new concept to me.
I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.
Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.
Check out my new course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, callbacks, nested workflows, design patterns and best practices.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong