<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Brokers on Inorderly.com</title>
    <link>https://inorderly.com/tags/brokers/</link>
    <description>Recent content in Brokers on Inorderly.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 02 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://inorderly.com/tags/brokers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Inorderly 0.2 Orders Events Straight From Kafka, NATS and Redis Streams</title>
      <link>https://inorderly.com/inorderly-0.2-orders-events-straight-from-kafka-nats-and-redis-streams/</link>
      <pubDate>Mon, 02 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://inorderly.com/inorderly-0.2-orders-events-straight-from-kafka-nats-and-redis-streams/</guid>
      <description>&lt;p&gt;The events that need ordering mostly don&amp;rsquo;t live in files. They sit in a Kafka topic, a NATS stream or a Redis stream, and until now getting them through Inorderly meant a script in front of it and another one behind. That works until the run gets killed half way, and then nobody can say which lines made it out.&lt;/p&gt;&#xA;&lt;p&gt;Inorderly 0.2 talks to the brokers itself. &lt;code&gt;-in&lt;/code&gt; and &lt;code&gt;-out&lt;/code&gt; take a URL as well as a file: &lt;code&gt;kafka://&lt;/code&gt;, &lt;code&gt;nats://&lt;/code&gt; or &lt;code&gt;redis://&lt;/code&gt;, with TLS and passwords. The clients are written against Go&amp;rsquo;s standard library, so it&amp;rsquo;s still one binary with no dependencies, and there are no consumer groups to set up. Inorderly keeps where it got to in each input in its own checkpoint.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
