<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel>
<title>Blog | Sebastian Kaiser</title>
<link>https://sekaiser.github.io/</link>
<description>An engineering notebook about software, systems, and the people who build and depend on them.</description>
<atom:link href="https://sekaiser.github.io/rss.xml" rel="self" type="application/rss+xml"/>
<item>
<title>The design decisions behind djob</title>
<link>https://sekaiser.github.io/notes/design-decisions-behind-djob.html</link>
<guid isPermaLink="false">urn:berlin:rss:983b3c85c517f35bed2ba3f9b07ec9344e953189276b0760172cae207f701036</guid>
<pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate>
<description>The reasoning behind djob's replicated coordination, independent workers, shared-resource reservations and release selection, with a worked capacity model and explicit recovery costs.</description>
<dc:creator>Sebastian Kaiser</dc:creator>
<category>distributed-systems</category>
<category>go</category>
<category>system-design</category>
</item>
<item>
<title>Durable distributed jobs and the design of djob</title>
<link>https://sekaiser.github.io/notes/durable-distributed-jobs.html</link>
<guid isPermaLink="false">urn:berlin:rss:4724cb677ce9f5aee8fe147b0366b7d41dee8127a51432c0c9f0272293521734</guid>
<pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate>
<description>Comparing Temporal, Dapr, two HTTP job schedulers and djob through research-based criteria, then following a gateway job through execution, uncertainty and recovery.</description>
<dc:creator>Sebastian Kaiser</dc:creator>
<category>distributed-systems</category>
<category>durable-execution</category>
<category>go</category>
<category>job-scheduling</category>
</item>
<item>
<title>Keeping current data useful</title>
<link>https://sekaiser.github.io/notes/keeping-current-data-useful.html</link>
<guid isPermaLink="false">urn:berlin:rss:e23b42aeee8ddab88ad7f7ae2c1f0bcd5d79e1f01387e8c4f30eb44e8fcd3ccd</guid>
<pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate>
<description>A reading path through current-state caches, overload and read visibility, starting with what people need from the data.</description>
<dc:creator>Sebastian Kaiser</dc:creator>
<category>backpressure</category>
<category>system-design</category>
<category>telemetry</category>
</item>
<item>
<title>From a service change to a shared release</title>
<link>https://sekaiser.github.io/notes/from-a-service-change-to-a-shared-release.html</link>
<guid isPermaLink="false">urn:berlin:rss:a0567be947236d38411c7023f3cdeb846cebf6008ef78cd9975356facd2ca21b</guid>
<pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate>
<description>A reading path from understandable Go services and agent-assisted changes to the evidence teams need for a shared release.</description>
<dc:creator>Sebastian Kaiser</dc:creator>
<category>architecture</category>
<category>software-delivery</category>
<category>testing</category>
</item>
<item>
<title>How I structure Go microservices for change</title>
<link>https://sekaiser.github.io/notes/go-microservices-for-change.html</link>
<guid isPermaLink="false">urn:berlin:rss:e6dcbb7f4bd2428a9a98b9d1251b8fc4dc61636df2a5441d5b59e5b24493cbb9</guid>
<pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate>
<description>Keeping Go services understandable and testable, so another engineer can change them safely and review work delegated to a coding agent.</description>
<dc:creator>Sebastian Kaiser</dc:creator>
<category>architecture</category>
<category>go</category>
<category>testing</category>
</item>
<item>
<title>The Iterator Is the State Machine</title>
<link>https://sekaiser.github.io/notes/the-iterator-is-the-state-machine.html</link>
<guid isPermaLink="false">urn:berlin:rss:ad49906b04141b94d1b83042253167075093ba662ee52fb5163156c7444a9090</guid>
<pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate>
<description>How Rust's Iterator trait supports lazy composition, and what a comparison with C++ ranges tells us about ownership checks and optimization.</description>
<dc:creator>Sebastian Kaiser</dc:creator>
<category>api-design</category>
<category>iterators</category>
<category>rust</category>
</item>
<item>
<title>Fast Writes, Fresh Reads</title>
<link>https://sekaiser.github.io/notes/fast-writes-fresh-reads.html</link>
<guid isPermaLink="false">urn:berlin:rss:d373db2ece53af1fab6b09603cde3f587d7584931a19518f0600469d205ef99c</guid>
<pubDate>Sat, 24 Oct 2026 00:00:00 GMT</pubDate>
<description>Why an accepted write can still leave a dashboard behind, explored through a small journal design in Go and Rust.</description>
<dc:creator>Sebastian Kaiser</dc:creator>
<category>backpressure</category>
<category>concurrency</category>
<category>storage</category>
</item>
<item>
<title>Backpressure in a Telemetry Pipeline: What Happens When the Cache Falls Behind?</title>
<link>https://sekaiser.github.io/notes/backpressure-in-a-telemetry-pipeline.html</link>
<guid isPermaLink="false">urn:berlin:rss:283ee638244853675609d9779ca98473446f3e972da78712f0825d7f43ba2ff0</guid>
<pubDate>Tue, 20 Oct 2026 00:00:00 GMT</pubDate>
<description>Keeping cache work bounded without hiding what readers lose when telemetry updates are discarded or arrive late.</description>
<dc:creator>Sebastian Kaiser</dc:creator>
<category>backpressure</category>
<category>concurrency</category>
<category>system-design</category>
</item>
<item>
<title>From Time-Series to State: Designing a Cache for Periodic Device Telemetry</title>
<link>https://sekaiser.github.io/notes/from-time-series-to-state.html</link>
<guid isPermaLink="false">urn:berlin:rss:ac84abd5c1ebcc8576a28d3b78fe1b26e3043d3d5b7b0e02fd904a180818e956</guid>
<pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate>
<description>Serving current device readings without reconstructing them from history, while keeping the age of each observation visible.</description>
<dc:creator>Sebastian Kaiser</dc:creator>
<category>caching</category>
<category>performance</category>
<category>telemetry</category>
</item>
<item>
<title>CI/CD Across Team Boundaries</title>
<link>https://sekaiser.github.io/notes/ci-cd-across-team-boundaries.html</link>
<guid isPermaLink="false">urn:berlin:rss:29ce98c0cbceb192b42d44f471a34601024cd3128b793982388e29ac4f560046</guid>
<pubDate>Sat, 03 Oct 2026 00:00:00 GMT</pubDate>
<description>How teams can check a shared customer journey while keeping control of their services, and understand when passing tests support a release decision.</description>
<dc:creator>Sebastian Kaiser</dc:creator>
<category>ci-cd</category>
<category>software-delivery</category>
<category>testing</category>
</item>
<item>
<title>Publishing from Org</title>
<link>https://sekaiser.github.io/notes/publishing-from-org.html</link>
<guid isPermaLink="false">urn:berlin:rss:e75e333cd9bc54c304cdf5f8056861f4bba4adac6e36a65e619e28359636b08f</guid>
<pubDate>Tue, 08 Sep 2026 00:00:00 GMT</pubDate>
<description>A path through the notebook’s Org publishing examples: inspect what survives export, see it in a working article, and distinguish stored results from live execution.</description>
<dc:creator>Sebastian Kaiser</dc:creator>
<category>emacs</category>
<category>org-mode</category>
<category>publishing</category>
</item>
<item>
<title>Org-mode publishing showcase</title>
<link>https://sekaiser.github.io/notes/org-mode-publishing-showcase.html</link>
<guid isPermaLink="false">urn:berlin:rss:69e5a46ad0a2fee07f9d2c91c126475860012ea3fd75b111e895f9ce09a23874</guid>
<pubDate>Thu, 25 May 2023 00:00:00 GMT</pubDate>
<description>What survives the journey from an Emacs buffer to a web page? Inspect headings, tables, task states, and source code in this working Org-mode publishing fixture.</description>
<dc:creator>Sebastian Kaiser</dc:creator>
<category>emacs</category>
<category>org-mode</category>
<category>publishing</category>
</item>
<item>
<title>Processing JSON with Rust</title>
<link>https://sekaiser.github.io/notes/processing-json-with-rust.html</link>
<guid isPermaLink="false">urn:berlin:rss:9da5e44d49fcb875dc7f6b47fa2f1e9de051f532dc8797f49a52e1aeb774149c</guid>
<pubDate>Thu, 25 May 2023 00:00:00 GMT</pubDate>
<description>A Rust learning exercise with nested Olympic JSON: read country fields, count medals and rank results, with a worked example to follow.</description>
<dc:creator>Sebastian Kaiser</dc:creator>
<category>rust</category>
<category>serde-json</category>
</item>
</channel></rss>
