<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Nats on Damian Maclennan</title>
    <link>http://damianm.com/tags/nats/</link>
    <description>Recent content in Nats on Damian Maclennan</description>
    <generator>Hugo</generator>
    <language>en-au</language>
    <managingEditor>damian@damianm.com (Damian Maclennan)</managingEditor>
    <lastBuildDate>Mon, 04 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://damianm.com/tags/nats/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Nimbus now supports NATS.io</title>
      <link>http://damianm.com/posts/2026/nimbus-now-supports-nats-io/</link>
      <pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate>
      <guid>http://damianm.com/posts/2026/nimbus-now-supports-nats-io/</guid>
      <description>&lt;![CDATA[<p>I just shipped a new <a href="https://nimbusapi.com/docs/transports/nats/">Nimbus</a> transport for the <a href="https://nats.io/">NATS</a> messaging system.</p>
<p>It&rsquo;s something I&rsquo;ve wanted to do for a long time, and with this release, I think it makes <a href="https://nimbusapi.com">Nimbus</a> an excellent option for using NATS on .NET.</p>
<p>The NATS C# client is excellent, but if you want to build it in to your applications you still need to manage queue topology, retries, and message dispatch within your own code. Nimbus makes all of this really easy, so you can just worry about your own logic and it takes care of the plumbing.</p>
<p>I also give you the choice of using the faster NATS Core backend, or the persistent and robust JetStream storage option. There&rsquo;s full documentation on the <a href="https://nimbusapi.com/docs/transports/nats/">Nimbus site</a>.</p>
<p>NATS is a great project, it&rsquo;s lightweight, massively high throughput, and I&rsquo;ve really seen it get some traction of late. I&rsquo;ve been following <a href="https://x.com/derekcollison">Derek Collison&rsquo;s</a> journey with NATS for years and years now, and I always thought it would be great to add it to Nimbus.</p>
<p>The work I did cleaning up the integration suite recently has removed so much friction to adding new transport layers and making sure I can adapt the infrastructure to Nimbus&rsquo;s semantics.</p>
<p>So the timing was good, and now it&rsquo;s happened.</p>
<p>If this is something that&rsquo;s interesting, I&rsquo;d love to hear from you.</p>
]]></description>
      <content:encoded>&lt;![CDATA[<p>I just shipped a new <a href="https://nimbusapi.com/docs/transports/nats/">Nimbus</a> transport for the <a href="https://nats.io/">NATS</a> messaging system.</p>
<p>It&rsquo;s something I&rsquo;ve wanted to do for a long time, and with this release, I think it makes <a href="https://nimbusapi.com">Nimbus</a> an excellent option for using NATS on .NET.</p>
<p>The NATS C# client is excellent, but if you want to build it in to your applications you still need to manage queue topology, retries, and message dispatch within your own code. Nimbus makes all of this really easy, so you can just worry about your own logic and it takes care of the plumbing.</p>
<p>I also give you the choice of using the faster NATS Core backend, or the persistent and robust JetStream storage option. There&rsquo;s full documentation on the <a href="https://nimbusapi.com/docs/transports/nats/">Nimbus site</a>.</p>
<p>NATS is a great project, it&rsquo;s lightweight, massively high throughput, and I&rsquo;ve really seen it get some traction of late. I&rsquo;ve been following <a href="https://x.com/derekcollison">Derek Collison&rsquo;s</a> journey with NATS for years and years now, and I always thought it would be great to add it to Nimbus.</p>
<p>The work I did cleaning up the integration suite recently has removed so much friction to adding new transport layers and making sure I can adapt the infrastructure to Nimbus&rsquo;s semantics.</p>
<p>So the timing was good, and now it&rsquo;s happened.</p>
<p>If this is something that&rsquo;s interesting, I&rsquo;d love to hear from you.</p>
]]></content:encoded>
    </item>
    
  </channel>
</rss>
