<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reliability on Enrique Goberna</title><link>https://enriquegoberna.com/tags/reliability/</link><description>Recent content in Reliability on Enrique Goberna</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 21 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://enriquegoberna.com/tags/reliability/index.xml" rel="self" type="application/rss+xml"/><item><title>When Postgres Is Enough: Building a Resilient Snapshot Ingestion Pipeline Without Kafka</title><link>https://enriquegoberna.com/posts/when-postgres-is-enough-building-a-resilient-snapshot-ingestion-pipeline-without-kafka/</link><pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate><guid>https://enriquegoberna.com/posts/when-postgres-is-enough-building-a-resilient-snapshot-ingestion-pipeline-without-kafka/</guid><description>&lt;p&gt;It has been a while.&lt;/p&gt;
&lt;p&gt;The last few months have been busy, and I have not published as much as I would have liked. Now that I have a bit more time, I wanted to come back with a topic I keep finding interesting in backend design: knowing when &lt;strong&gt;not&lt;/strong&gt; to add more infrastructure.&lt;/p&gt;
&lt;p&gt;This post is about a small but useful architectural decision: building a resilient snapshot ingestion pipeline without introducing Kafka or a message broker from day one.&lt;/p&gt;</description></item></channel></rss>