<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Architecture on Guido Battiston</title>
		<link>https://guidobattiston.com/tags/architecture/</link>
		<description>Recent content in Architecture on Guido Battiston</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Sun, 05 Jul 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://guidobattiston.com/tags/architecture/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Deterministic Simulation Testing in Go with synctest</title>
				<link>https://guidobattiston.com/posts/dst-go/</link>
				<pubDate>Sun, 05 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://guidobattiston.com/posts/dst-go/</guid>
				<description>&lt;p&gt;Concurrency bugs are miserable to test for. A test passes on your machine, fails once in CI, and you can&amp;rsquo;t reproduce it because it lived in some interleaving the scheduler picked that one time. Deterministic Simulation Testing (DST) is one way out of that. The idea is to take the things in your program that vary between runs and funnel them through a single bus, one operation at a time, all driven by a seed. Fix the seed and you get the same run back, so a failure stops being a fluke and becomes something you can replay and debug properly.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
