<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Mpsc - Tag - Roland's Dev Blog</title><link>https://rolandsdev.blog/tags/mpsc/</link><description>Mpsc - Tag - Roland's Dev Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 16 Sep 2026 09:00:00 +0900</lastBuildDate><atom:link href="https://rolandsdev.blog/tags/mpsc/" rel="self" type="application/rss+xml"/><item><title>Build resiliency and delivery guarantees in distributed systems</title><link>https://rolandsdev.blog/posts/delivery-guarantees-in-distributed-systems/</link><pubDate>Wed, 16 Sep 2026 09:00:00 +0900</pubDate><author><name>rolandjitsu</name><uri>https://github.com/rolandjitsu</uri><email>rolandjitsu@gmail.com</email></author><guid>https://rolandsdev.blog/posts/delivery-guarantees-in-distributed-systems/</guid><description><![CDATA[<p>I&rsquo;ve been spending a bit more time lately - whatever little spare time I have outside work and family - on a few open source projects. One of them is <a href="https://github.com/rolandjitsu/persistent-queue" target="_blank" rel="noopener noreferrer">persistent-queue</a>: a durable, at-least-once, MPSC queue.</p>
<p>I wanted to take some time to explain the story behind it.</p>
<p>For the past few years I&rsquo;ve been working on very similar systems, though in different industries: telemetry collection and ingestion from edge devices. And every single time, the same scenarios came up:</p>]]></description></item></channel></rss>