Bringing @workflow to your Kubernetes

Workflows look easy… until they corrupt your data. Durable workflows in Node.js promise retries, persistence, and long-running execution. On platforms like Vercel, everything just works. But the moment you move to Kubernetes, a hidden problem appears: version mismatch. A small code change can replay the wrong steps, mix results, and silently break your system. The question: how do you run durable workflows safely in production? Luca Maraschi and Matteo Collina dive into workflow orchestration in Node.js and the real challenges behind deterministic execution. From Workflow DevKit to Platformatic World, they break down how version-safe workflows work on Kubernetes, ensuring every run is pinned to the exact code version that created it, even across deployments, retries, and long-running jobs. In this episode, we cover: ✅ Why durable workflows break on Kubernetes and not on Vercel ✅ How deterministic replay works and why it can corrupt data ✅ The hidden problem of versioning in long-running workflows ✅ How Platformatic World enables version-safe orchestration ✅ Why queue routing is critical for workflow correctness ✅ What zero-config workflows look like in real production systems If you're building with Node.js, Kubernetes, or event-driven architectures, this episode is for you. Durable workflows are powerful, but without version safety, they’re a risk. This is what it actually takes to run them in production.