Tweet Note: see here for the rest of the series.   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 – all the while there was a fully armed sales team before there was even a product!

Tweet 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

Tweet 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. AWS Lambda – compare coldstart time with different languages, memory and code sizes It is a fantastic

Tweet A while back we looked at the performance difference between the language runtimes AWS Lambda supports natively. AWS Lambda – comparing platform performances 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

Tweet TL;DR – The no. of partitions in a DynamoDB table goes up in response to increased load or storage size, but it never come back down, ever. DynamoDB is pretty great, but as I have seen this particular problem at 3 different companies – Gamesys, JUST EAT, and now Space Ape Games – I think