<?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 Rafiul Alam</title>
    <link>https://alamrafiul.com/tags/nats/</link>
    <description>Recent content in Nats on Rafiul Alam</description>
    <image>
      <title>Rafiul Alam</title>
      <url>https://alamrafiul.com/papermod-cover.png</url>
      <link>https://alamrafiul.com/papermod-cover.png</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Mon, 23 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://alamrafiul.com/tags/nats/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Messaging Systems: A Visual Reference</title>
      <link>https://alamrafiul.com/posts/messaging-systems-visual-guide/</link>
      <pubDate>Mon, 23 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://alamrafiul.com/posts/messaging-systems-visual-guide/</guid>
      <description>15 messaging scenarios with increasing complexity — Kafka, RabbitMQ, and JetStream NATS compared through diagrams. Less words, more architecture.</description>
    </item>
    
    <item>
      <title>Building Scalable Event-Driven Microservices in Go: A User and Notes Service Example</title>
      <link>https://alamrafiul.com/posts/event-driven-microservices-go/</link>
      <pubDate>Wed, 15 Oct 2025 00:00:00 +0000</pubDate>
      
      <guid>https://alamrafiul.com/posts/event-driven-microservices-go/</guid>
      <description>Learn how to build scalable, resilient event-driven microservices in Go using NATS JetStream, Watermill, Bun ORM, and PostgreSQL with practical User and Notes service examples.</description>
    </item>
    
    <item>
      <title>NATS &amp; JetStream in Go: Cloud-Native Messaging at Scale</title>
      <link>https://alamrafiul.com/posts/nats-jetstream/</link>
      <pubDate>Fri, 07 Feb 2025 00:00:00 +0000</pubDate>
      
      <guid>https://alamrafiul.com/posts/nats-jetstream/</guid>
      <description>Master NATS and JetStream in Go: subject-based messaging, pub/sub patterns, at-most-once vs at-least-once delivery, stream processing, and high-throughput microservices orchestration.</description>
    </item>
    
    <item>
      <title>Event-Driven Note Sharing: Building Real-Time Microservices with NATS, Go, and Vue.js</title>
      <link>https://alamrafiul.com/blogs/nats-event-driven-notes/</link>
      <pubDate>Mon, 27 Jan 2025 00:00:00 +0000</pubDate>
      
      <guid>https://alamrafiul.com/blogs/nats-event-driven-notes/</guid>
      <description>&lt;p&gt;Building a real-time note-sharing application is a perfect use case for exploring event-driven architecture. In this comprehensive guide, we&amp;rsquo;ll build a production-ready system with two microservices (User and Note services) that communicate through NATS, delivering instant updates to a Vue.js frontend.&lt;/p&gt;
&lt;h2 id=&#34;why-event-driven-architecture&#34;&gt;Why Event-Driven Architecture?&lt;/h2&gt;
&lt;p&gt;Traditional request-response patterns create tight coupling between services. When your Note service needs to notify users about changes, you don&amp;rsquo;t want to make synchronous HTTP calls to every service that cares about notes. Event-driven architecture solves this with loose coupling:&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
