PinnedLong Quanzheng·Aug 21, 2023Guide to ContinueAsNew in Cadence/Temporal workflow, using iWF as an example — Part 1NOTE: this post uses “Temporal” to represent both Cadence and Temporal to make it easier to read.A response icon1A response icon1
PinnedLong Quanzheng·Apr 25, 2025Why Modern Workflow Frameworks Are Essential for Today’s Backend EngineeringNOTE: iWF is now forked as Dex (Durable-Execution).A response icon1A response icon1
PinnedLong Quanzheng·Apr 25, 2025iWF Overview for Temporal Users-Part1: Programming Model DifferenceNOTE: iWF is now forked as Dex (Durable-Execution).
PinnedLong Quanzheng·Apr 24, 202514 “Modern” Backend Software Design Patterns with Indeed Workflow Framework(iWF) on TemporalNOTE: iWF is now forked as Dex (Durable-Execution).
PinnedLong Quanzheng·Dec 30, 2022Why I created Indeed Workflow Framework(iWF)NOTE: iWF is now forked as Dex (Durable-Execution).
Long Quanzheng·Oct 16Temporal on Aurora Limitless: Postgres That Scales OutWe ported Temporal’s SQL persistence to Aurora PostgreSQL Limitless, tested every database behavior Temporal relies on, and worked out what…
Long Quanzheng·Jun 4Fault tolerance in LangGraph: retries, timeouts, and error handlersA clone from LangChain blog, co-authored by Sydney Runkle.
Long Quanzheng·Aug 20, 2025Workflow Should be Code, but Replay Based Durable Execution is NOT the ONLY wayNOTE: iWF is now forked as Dex (Durable-Execution).
Long Quanzheng·Apr 25, 2025iWF Overview for Temporal Users-Part2: Architectural DifferenceNOTE: iWF is now forked as Dex (Durable-Execution).
Long Quanzheng·Apr 25, 2025Wait For State Completion Design Pattern in iWFIn modern distributed systems, coordinating between clients and long-running background workflow executions presents significant…