Tweet 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

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

Over the last year, I have been working on The Gamma project, which aims to make data-driven visualizations more trustworthy and to enable large number of people to build visualizations backed by data. The Gamma makes it possible to create visualizations that are built on trustworthy primary data sources such as the World Bank and you can provide your own data source by writing a REST service. A great piece of feedback that I got when talking about The Gamma is that this is a nice ultimate goal, but it mak[...]