<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Workflow Engine on 卓琪的开发笔记</title>
    <link>https://zhuoqidev.com/tags/workflow-engine/</link>
    <description>Recent content in Workflow Engine on 卓琪的开发笔记</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>zh-CN</language>
    <copyright>© 2026 Liu ZhuoQi</copyright>
    <lastBuildDate>Sat, 16 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://zhuoqidev.com/tags/workflow-engine/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Why We Moved from Celery to Temporal for Production Agent Pipelines</title>
      <link>https://zhuoqidev.com/en/posts/why-temporal-not-celery/</link>
      <pubDate>Sat, 16 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://zhuoqidev.com/en/posts/why-temporal-not-celery/</guid>
      <description>&lt;p&gt;In April 2026, we migrated seo-project&amp;rsquo;s task queue from Celery to Temporal. We dropped exactly one dependency (&lt;code&gt;celery&lt;/code&gt;), wrote 11 new files (&lt;code&gt;src/infrastructure/temporal/&lt;/code&gt;), and renamed our containers from &lt;code&gt;api/worker/beat&lt;/code&gt; to &lt;code&gt;api/temporal_worker_blue/green&lt;/code&gt; with blue-green deployment.&lt;/p&gt;&#xA;&lt;p&gt;The most common question afterward: &lt;strong&gt;why not just keep using Celery? If it&amp;rsquo;s already running, what&amp;rsquo;s the point?&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;This article is the answer. It doesn&amp;rsquo;t come from documentation comparisons. It comes from production bugs we hit running Agent pipelines at scale.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
