<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Durable Execution on Nejc Korasa</title><link>https://nejckorasa.github.io/tags/durable-execution/</link><description>Recent content in Durable Execution on Nejc Korasa</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Nejc Korasa</copyright><lastBuildDate>Fri, 17 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://nejckorasa.github.io/tags/durable-execution/index.xml" rel="self" type="application/rss+xml"/><item><title>A Practical Introduction to Temporal for Teams Going Async</title><link>https://nejckorasa.github.io/posts/temporal-going-async/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://nejckorasa.github.io/posts/temporal-going-async/</guid><description>&lt;p&gt;If your team is moving from a single synchronous service into distributed, asynchronous, event-driven systems, you&amp;rsquo;re about to inherit a class of problems that used to be someone else&amp;rsquo;s: work that fails halfway through, steps that must not run twice, calls that return before the work is actually done. &lt;strong&gt;Temporal&lt;/strong&gt; is a durable execution engine that tames a lot of this - you define a multi-step process, and it guarantees that process runs to completion even when workers crash in the middle.&lt;/p&gt;</description></item></channel></rss>