<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Temporal on How It Works</title>
    <link>https://backend.how/tags/temporal/</link>
    <description>Recent content in Temporal on How It Works</description>
    <generator>Hugo</generator>
    <language>en</language>
    <managingEditor>pg@backend.how (Pratik)</managingEditor>
    <webMaster>pg@backend.how (Pratik)</webMaster>
    <copyright>backend.how © 2026 by Pratik is licensed under CC BY-SA 4.0</copyright>
    <lastBuildDate>Sun, 05 Apr 2026 12:00:00 +0530</lastBuildDate>
    <atom:link href="https://backend.how/tags/temporal/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>🚂 Temporal — Under the Hood</title>
      <link>https://backend.how/posts/temporal-under-the-hood/</link>
      <pubDate>Sun, 05 Apr 2026 12:00:00 +0530</pubDate><author>pg@backend.how (Pratik)</author>
      <guid>https://backend.how/posts/temporal-under-the-hood/</guid>
      <description>&lt;h1 id=&#34;what-youll-learn&#34;&gt; &#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#what-youll-learn&#34;&gt;&#xA;    &lt;span class=&#34;h-text&#34;&gt; What you&amp;rsquo;ll learn &lt;/span&gt; &#xA;    &lt;span class=&#34;pound&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&#xA;&lt;p&gt;Durable execution engines like &lt;a href=&#34;https://temporal.io/&#34;&gt;Temporal&lt;/a&gt; are&#xA;increasingly how backend teams handle multi-step workflows — payments,&#xA;order fulfilment, LLM agent loops, scheduled jobs. They make &amp;ldquo;run this&#xA;4-step thing, retry on failure, wait for a webhook on step 3&amp;rdquo; trivial to&#xA;express in code. That&amp;rsquo;s the pitch.&lt;/p&gt;&#xA;&lt;p&gt;The pitch makes the &lt;em&gt;cost&lt;/em&gt; invisible. By the time you ship, your Postgres&#xA;is handling an order of magnitude more queries than you expected, and&#xA;you&amp;rsquo;re not sure why.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
