Common Pitfalls with Durable Execution Frameworks, like Durable Functions or Temporal | by Chris Gillum | Medium

I recently came back from Temporal.io’s excellent Replay conference here in Seattle. It was great hearing from Temporal employees as well as their customers about the benefits and challenges of using “workflow-as-code” (sometimes also referred to as “code-as-workflow”) durable execution frameworks, like Temporal. As the creator of Azure Durable Functions, which is a similar project with the same historical roots, much of the discussion largely applied to the developers I work with as well. One of the biggest takeaways from this conference for me personally was confirmation about some of the biggest challenges that developers face when using this kind of replay-based durable execution technology in their applications. I thought it might be worth writing about some of these challenges as a way to both educate those who are exploring the technology as well as help me think more clearly about ways to solve them. Below are a few of the most heavily discussed challenges. Note that the conten

I recently came back from Temporal.io’s excellent Replay conference here in Seattle. It was great hearing from Temporal employees as well as their customers about the benefits and challenges of using “workflow-as-code” (sometimes also referred to as “code-as-workflow”) durable execution frameworks, like Temporal. As the creator of Azure Durable Functions, which is a similar project with the same historical roots, much of the discussion largely applied to the developers I work with as well. One of the biggest takeaways from this conference for me personally was confirmation about some of the bi