<?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>Microservices on Rafiul Alam</title>
    <link>https://alamrafiul.com/categories/microservices/</link>
    <description>Recent content in Microservices 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>Tue, 28 Jan 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://alamrafiul.com/categories/microservices/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building Microservices with gRPC and WebSocket Gateway: Connecting Vue.js to Go Services</title>
      <link>https://alamrafiul.com/blogs/grpc-websocket-gateway/</link>
      <pubDate>Tue, 28 Jan 2025 00:00:00 +0000</pubDate>
      
      <guid>https://alamrafiul.com/blogs/grpc-websocket-gateway/</guid>
      <description>&lt;p&gt;When building microservices, choosing the right communication protocol is crucial. While REST and event-driven architectures have their place, gRPC offers a compelling alternative with strong typing, efficient binary serialization, and built-in support for streaming. In this guide, we&amp;rsquo;ll build a complete note-sharing application using gRPC microservices in Go, with a Vue.js frontend connected through a WebSocket gateway.&lt;/p&gt;
&lt;h2 id=&#34;why-grpc-for-microservices&#34;&gt;Why gRPC for Microservices?&lt;/h2&gt;
&lt;p&gt;gRPC brings several advantages to microservice architectures:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Strong Typing&lt;/strong&gt;: Protocol Buffers provide type-safe contracts between services&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Performance&lt;/strong&gt;: Binary serialization is faster and more compact than JSON&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Code Generation&lt;/strong&gt;: Auto-generate client and server code from .proto files&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Streaming&lt;/strong&gt;: Built-in support for bidirectional streaming&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Language Agnostic&lt;/strong&gt;: Works across many programming languages&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;HTTP/2&lt;/strong&gt;: Connection multiplexing, header compression, and server push&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;However, browsers can&amp;rsquo;t make native gRPC calls. That&amp;rsquo;s where our WebSocket gateway comes in.&lt;/p&gt;</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>
