<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pub/Sub on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/pub/sub/</link><description>Recent content in Pub/Sub on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 14 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/pub/sub/index.xml" rel="self" type="application/rss+xml"/><item><title>Intermediate Topics: Publish/Subscribe (Pub/Sub)</title><link>https://ai-blog.noorshomelab.dev/redis-guide/redis-pubsub/</link><pubDate>Fri, 07 Nov 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/redis-guide/redis-pubsub/</guid><description>&lt;p&gt;Redis is not just a data store; it&amp;rsquo;s also a powerful &lt;strong&gt;message broker&lt;/strong&gt; through its &lt;strong&gt;Publish/Subscribe (Pub/Sub)&lt;/strong&gt; mechanism. Pub/Sub allows different parts of your application (or even entirely separate applications) to communicate in a decoupled, real-time fashion.&lt;/p&gt;
&lt;p&gt;In Pub/Sub:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Publishers&lt;/strong&gt; send messages to a &lt;code&gt;channel&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Subscribers&lt;/strong&gt; listen for messages on specific &lt;code&gt;channels&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;When a message is published to a channel, all subscribers to that channel immediately receive the message.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Key characteristics:&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Full-Stack JavaScript System Design Scenarios</title><link>https://ai-blog.noorshomelab.dev/js-architect-prep-2026/fullstack-javascript-system-design/</link><pubDate>Wed, 14 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/js-architect-prep-2026/fullstack-javascript-system-design/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 15: Full-Stack JavaScript System Design Scenarios. While previous chapters might have delved into the intricate &amp;ldquo;weird parts&amp;rdquo; of JavaScript at a granular level, this chapter elevates that understanding to an architectural plane. For senior and architect-level roles, it&amp;rsquo;s not enough to merely know how JavaScript&amp;rsquo;s event loop works; you must be able to design entire systems that leverage its strengths and mitigate its weaknesses.&lt;/p&gt;
&lt;p&gt;This chapter is designed for experienced developers aspiring to architect or lead positions. It focuses on applying deep knowledge of JavaScript&amp;rsquo;s execution model, asynchronous nature, memory management, and even its more unintuitive behaviors (like scope, closures, and &lt;code&gt;this&lt;/code&gt; binding) to solve complex full-stack system design challenges. We&amp;rsquo;ll explore how these fundamental concepts directly impact scalability, performance, reliability, and maintainability of real-world applications built with modern JavaScript (ES2025/2026 standards, Node.js v20+, React/Vue/Angular latest versions).&lt;/p&gt;</description></item></channel></rss>