Step Functions

Step Functions : apply try-catch to a block of states

In my last post we talked about how we can imple­ment sem­a­phores with Step Func­tions. Anoth­er com­mon sce­nario that many peo­ple have is to han­dle errors from a block of states like we’re used to with a try-catch block. try { step1() step2() step3() } catch (States.Timeout) { … } catch (States.ALL) { … } …

Step Func­tions : apply try-catch to a block of statesRead More »

Step Functions: how to implement semaphores for state machines

Here at DAZN, we are migrat­ing from our lega­cy plat­form into a brave new world of microfron­tends and microser­vices. Along the way, we also dis­cov­ered the delights that AWS Step Func­tion has to offer, for exam­ple… flex­i­ble error han­dling and retry the under­stat­ed abil­i­ty to wait between tasks the abil­i­ty to mix auto­mat­ed steps with …

Step Func­tions: how to imple­ment sem­a­phores for state machinesRead More »

Applying the Saga pattern with AWS Lambda and Step Functions

The Saga pat­tern is a pat­tern for man­ag­ing fail­ures, where each action has a com­pen­sat­ing action for roll­back. In Hec­tor Garcia-Molina’s 1987 paper, it is described as an approach to han­dling sys­tem fail­ures in a long-run­n­ing trans­ac­tions. It has become increas­ing­ly rel­e­vant in the world of microser­vices as appli­ca­tion log­ic often needs to trans­act across …

Apply­ing the Saga pat­tern with AWS Lamb­da and Step Func­tionsRead 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.

Close