<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nats on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/nats/</link>
    <description>Recent content in Nats on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 19 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/nats/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted NATS Server Administration: natscli vs nats-top vs nats-account-server</title>
      <link>https://www.pistack.xyz/posts/2026-05-19-self-hosted-nats-server-administration-natscli-nats-top-nats-account-server/</link>
      <pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-19-self-hosted-nats-server-administration-natscli-nats-top-nats-account-server/</guid>
      <description>&lt;p&gt;NATS has emerged as one of the most popular open-source messaging systems for cloud-native architectures, offering a simple yet powerful publish-subscribe and request-reply communication layer. With over 19,000 GitHub stars and adoption by major organizations, NATS powers everything from microservices communication to IoT data pipelines. But managing a production NATS deployment requires more than just starting the server &amp;ndash; you need proper administration, monitoring, and account management tools.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
