<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Messaging on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/messaging/</link><description>Recent content in Messaging on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 15 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/messaging/index.xml" rel="self" type="application/rss+xml"/><item><title>Service-to-Service Communication: Synchronous vs. Asynchronous</title><link>https://ai-blog.noorshomelab.dev/systems-engineering-2026/service-communication-sync-async/</link><pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/systems-engineering-2026/service-communication-sync-async/</guid><description>&lt;p&gt;Welcome back, aspiring systems architect! In the previous chapter, we explored how a reverse proxy acts as the intelligent front door to our services. Now, let&amp;rsquo;s venture deeper into the heart of distributed systems: &lt;strong&gt;how services talk to each other&lt;/strong&gt;. Just like people communicate in different ways – a quick chat versus sending a detailed email – services also have distinct communication styles. Choosing the right one is fundamental to building scalable, resilient, and performant applications, especially as we integrate advanced AI agent workflows.&lt;/p&gt;</description></item><item><title>6. Message Brokers and Service Interactions: Kafka and Web Services</title><link>https://ai-blog.noorshomelab.dev/testcontainers-mastery-2026/06-message-brokers-kafka-web-services/</link><pubDate>Sat, 14 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/testcontainers-mastery-2026/06-message-brokers-kafka-web-services/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid tester! In the previous chapters, you mastered the art of using Testcontainers to bring real databases into your tests. That was a huge step up from in-memory fakes, but what about the broader landscape of modern applications? Many microservices don&amp;rsquo;t just talk to databases; they communicate through message brokers, call other APIs, and integrate with external services.&lt;/p&gt;
&lt;p&gt;This chapter is your passport to confidently testing those complex interactions. We&amp;rsquo;re going to tackle two crucial areas:&lt;/p&gt;</description></item><item><title>Event-Driven Architectures: Building Reactive and Scalable Systems</title><link>https://ai-blog.noorshomelab.dev/systems-engineering-2026/event-driven-architectures/</link><pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/systems-engineering-2026/event-driven-architectures/</guid><description>&lt;h3 id="introduction-embracing-reactivity-for-modern-systems"&gt;Introduction: Embracing Reactivity for Modern Systems&lt;/h3&gt;
&lt;p&gt;Imagine a bustling city where every action immediately triggers a cascade of necessary responses without anyone having to wait. A taxi drops off a passenger, and immediately, its status updates, a new fare is assigned, and a billing record is created. This highly responsive, interconnected flow is the essence of an event-driven architecture (EDA). It&amp;rsquo;s how complex systems stay agile and responsive, even under immense load.&lt;/p&gt;</description></item><item><title>Advanced Topics: Redis Streams for Event Sourcing</title><link>https://ai-blog.noorshomelab.dev/redis-guide/redis-streams/</link><pubDate>Fri, 07 Nov 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/redis-guide/redis-streams/</guid><description>&lt;p&gt;In the &amp;ldquo;Publish/Subscribe&amp;rdquo; chapter, we learned about real-time, fire-and-forget messaging. While powerful for certain use cases, traditional Pub/Sub has a limitation: messages are not persisted. If a subscriber is offline, it misses messages. This is where &lt;strong&gt;Redis Streams&lt;/strong&gt; come in.&lt;/p&gt;
&lt;p&gt;Redis Streams, introduced in Redis 5.0, are a more robust, persistent, and highly scalable messaging solution. They are append-only data structures that act as a continuously growing log, similar in concept to Apache Kafka. Streams are ideal for:&lt;/p&gt;</description></item><item><title>11. Distributed Services and Event-Driven Architectures</title><link>https://ai-blog.noorshomelab.dev/void-cloud-mastery-2026/distributed-services-event-driven-architectures/</link><pubDate>Sat, 14 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/void-cloud-mastery-2026/distributed-services-event-driven-architectures/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid Void Cloud explorer! In our previous chapters, we&amp;rsquo;ve mastered deploying individual services, managing environments, and optimizing performance. You&amp;rsquo;ve built robust applications, but what happens when your application needs to handle millions of users, process vast amounts of data, or integrate with dozens of other services? That&amp;rsquo;s where the power of distributed services and event-driven architectures truly shines.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;re going to dive deep into these advanced architectural patterns. We&amp;rsquo;ll learn how to break down monolithic applications into smaller, independent services that communicate asynchronously. You&amp;rsquo;ll discover how Void Cloud provides the perfect foundation for building highly scalable, resilient, and maintainable systems using its suite of managed services like Void Functions, Void Messaging, and Void Data Streams. Get ready to think beyond single applications and embrace the world of interconnected, intelligent services!&lt;/p&gt;</description></item></channel></rss>