[{"data":1,"prerenderedAt":75},["ShallowReactive",2],{"term-d\u002Fdurable-execution":3,"related-d\u002Fdurable-execution":59},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":44,"meta":45,"navigation":46,"path":47,"related":48,"seo":53,"sitemap":54,"stem":57,"subcategory":6,"__hash__":58},"terms\u002Fterms\u002Fd\u002Fdurable-execution.md","Durable Execution",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 - The Vibe Check",[16,17,18],"p",{},"Normal code forgets everything the moment the process crashes, so a long workflow like charge the card, wait three days, then ship the order falls apart if the server restarts halfway through. Durable execution frameworks checkpoint every step so the function can resume exactly where it left off, even after a crash, a deploy, or a three-day wait, without you writing any of the retry or state-saving logic yourself.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"Durable execution is a programming model where a workflow's state and progress are automatically persisted after every step, allowing execution to resume exactly where it left off after a crash, restart, or long delay. Frameworks like Temporal, Restate, and AWS Step Functions implement this by replaying an event history to reconstruct in-memory state rather than requiring developers to manually checkpoint progress.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"We rewrote the onboarding flow with durable execution so it survives deploys mid-flight.\" \u002F \"Temporal replays the event history to figure out exactly where the workflow crashed.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"backend","Normal code forgets everything the moment the process crashes, so a long workflow like charge the card, wait three days, then ship the order falls apart if...","advanced","md","d",{},true,"\u002Fterms\u002Fd\u002Fdurable-execution",[49,50,51,52],"Workflow Engine","Saga Pattern","Idempotency","Event Sourcing",{"title":5,"description":41},{"changefreq":55,"priority":56},"weekly",0.7,"terms\u002Fd\u002Fdurable-execution","QnjZ1h_NmDk_ergin-4odmnZQJq23iSn57gnstP2nRk",[60,64,68,71],{"title":52,"path":61,"acronym":6,"category":62,"difficulty":42,"description":63},"\u002Fterms\u002Fe\u002Fevent-sourcing","architecture","Instead of storing 'balance: $100', event sourcing stores 'deposited $200, withdrew $50, withdrew $50'.",{"title":51,"path":65,"acronym":6,"category":40,"difficulty":66,"description":67},"\u002Fterms\u002Fi\u002Fidempotency","intermediate","Idempotency means doing the same thing twice gives you the same result as doing it once.",{"title":50,"path":69,"acronym":6,"category":62,"difficulty":42,"description":70},"\u002Fterms\u002Fs\u002Fsaga-pattern","The saga pattern is how you handle transactions that span multiple services. In a monolith, you'd wrap everything in one database transaction.",{"title":49,"path":72,"acronym":6,"category":73,"difficulty":66,"description":74},"\u002Fterms\u002Fw\u002Fworkflow-engine","cloud","A workflow engine executes a series of steps in a defined order, handling branching, retries, timeouts, and failures.",1792528080592]