<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Rabbitmq on Blogfolio Najib</title>
		<link>https://najib.id/en/tags/rabbitmq/</link>
		<description>Recent content in Rabbitmq on Blogfolio Najib</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
			<copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright>
		
		
			<lastBuildDate>Thu, 10 Sep 2026 16:50:44 +0700</lastBuildDate>
		
			<atom:link href="https://najib.id/en/tags/rabbitmq/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Hijrah Backend (7): From TCP Packets to a Time-Series Database</title>
				<link>https://najib.id/en/writing/2026/hijrah-backend-07/</link>
				<pubDate>Thu, 10 Sep 2026 15:30:00 +0700</pubDate>
				<guid>https://najib.id/en/writing/2026/hijrah-backend-07/</guid>
				<description>&lt;p&gt;Every second, the fleet talks. Tens of thousands of GPS trackers send TCP packets carrying positions, ignition status, signal strength, and the system must swallow all of it, around the clock, with no &amp;ldquo;please send less data&amp;rdquo; campaign hahaha.&lt;/p&gt;&#xA;&lt;p&gt;In &lt;a href=&#34;https://najib.id/en/writing/2026/hijrah-backend-01/&#34;&gt;episode one&lt;/a&gt; I mentioned it briefly: the old system received and wrote within a single service. The new system splits that into three stages: a listener that only receives and decodes packets; a message queue in the middle; and a consumer that writes to the database. This episode walks through each stage, including two moments where I tripped, classically hehe~&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
