<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mohbaba on Medium]]></title>
        <description><![CDATA[Stories by Mohbaba on Medium]]></description>
        <link>https://medium.com/@babamu09?source=rss-93463fe3eea2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3MvloSPHpsogy6Q1kr3Dxw.jpeg</url>
            <title>Stories by Mohbaba on Medium</title>
            <link>https://medium.com/@babamu09?source=rss-93463fe3eea2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:04:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@babamu09/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Making Service Communication Effortless with Enterprise Messaging Systems]]></title>
            <link>https://medium.com/@babamu09/making-service-communication-effortless-with-enterprise-messaging-systems-93054cfb8fb4?source=rss-93463fe3eea2------2</link>
            <guid isPermaLink="false">https://medium.com/p/93054cfb8fb4</guid>
            <category><![CDATA[message-queue]]></category>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[message-broker]]></category>
            <category><![CDATA[messaging]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Mohbaba]]></dc:creator>
            <pubDate>Sun, 24 Nov 2024 19:01:36 GMT</pubDate>
            <atom:updated>2024-11-24T19:01:36.762Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yvruASN4DRaXivOOK8uZ_w.png" /><figcaption><em>image gotten from: cometChat</em></figcaption></figure><p>When we hear the term “messaging,” what usually comes to mind is sending messages on WhatsApp, Facebook, or other social media platforms. Messaging in this context solves various communication challenges — like the need for real-time interaction, quickly sharing information, and connecting people across languages and cultures. This has greatly revolutionized businesses, enabling them to contact customers for feedback or resolve issues efficiently, among other things.</p><p>What I’m writing about today, though, is a different type of messaging system: <strong>Enterprise Messaging Systems</strong>.</p><p><strong>Enterprise Messaging Systems (EMS)</strong> are designed to help services communicate (send and receive messages) in an asynchronous manner.</p><h4>Before EMS: The Old Way of Communication</h4><p>Originally, before EMSs came into the picture, services (or servers) communicated differently — through something called <strong><em>Remote Procedure Calls (RPC)</em></strong>.</p><p>RPC is a protocol that allows a program to execute a function on another server or computer without needing the developer to explicitly code the communication details. A simple example would be REST-based services communicating through endpoints.</p><p>Here’s how that worked: <br>- A client (like a web app or another server) would call the endpoint of a <strong>remote server</strong> and wait for its response before continuing. <br>- While it got the job done, this approach had some major downsides: <br> 1. The client had to <strong>wait</strong> for the server’s response, which made applications slow and less efficient. <br> 2. If the server wasn’t available, the communication failed entirely. This forced programmers to write defensive code to handle such cases, making the system more complex.</p><h4><strong>How EMS Changed the Game</strong></h4><p>EMS was designed to solve these problems. Instead of direct communication between client and server, EMS introduces an <strong><em>intermediate service </em></strong>that acts like a postman.</p><p>Here’s how it works: <br>1. When a client wants to send data, it publishes a message to the EMS (the postman). <br>2. The EMS delivers the message to the destination server, which processes it when it’s ready. <br>3. If the server has a response, it can publish that back to the EMS for delivery to the original client.</p><p>This mechanism promotes <strong><em>loose coupling </em></strong>between services, meaning they don’t have to depend on each other being available at the same time. Everything happens asynchronously, which is a huge improvement!</p><h4>Examples in Action</h4><p>Let’s make this more relatable with a simple example:</p><p>Imagine an e-commerce platform where a user places an order. The order needs to trigger several actions, like: <br>1. <strong>Payment Processing</strong>: Verify and deduct the amount from the user’s account. <br>2. <strong>Inventory Updates</strong>: Reserve the purchased items. <br>3. <strong>Shipping Notifications</strong>: Notify the warehouse to prepare the shipment. <br>4. <strong>Customer Communication</strong>: Send an email or SMS confirming the order.</p><p>With EMS, the system doesn’t handle all of this sequentially. Instead: <br>- The <strong>Order Service </strong>publishes a message to the EMS. <br>- Other services like payment, inventory, shipping, and notifications subscribe to the relevant queue and process the message independently. <br>This way, each service works asynchronously without waiting for another to finish its job.</p><h4>Why EMS is a big deal</h4><p>Here’s a quick summary of why EMS systems are so powerful: <br>1. <strong>Asynchronous Communication</strong>: No need to wait for responses — services can continue processing while waiting for messages to be delivered. <br>2. <strong>Fault Tolerance</strong>: If a service is down, EMS retains the message and ensures delivery when the service comes back online. <br>3. <strong>Scalability</strong>: Add more servers to handle increased load without affecting the core system. <br>4. <strong>Decoupling</strong>: Services don’t need to know about each other’s state or availability, simplifying maintenance. <br>5. <strong>Real-Time Event Handling</strong>: EMS makes event-driven architecture possible, allowing systems to react to events as they happen.</p><h4>Tools of the Trade</h4><p>There are several powerful tools that make EMS possible, and each comes with its strengths: <br>- <strong>RabbitMQ</strong>: A reliable, open-source message broker based on AMQP (Advanced Message Queuing Protocol). <br>- <strong>Apache Kafka</strong>: Great for distributed, high-throughput messaging and real-time event streaming. <br>- <strong>Apache Pulsar</strong>: A newer player offering multi-tenancy, geo-replication, and high scalability. It’s gaining traction for its advanced features. <br>- <strong>Amazon SQS</strong>: A fully managed queue service from AWS that handles scaling and reliability for you.</p><p>Enterprise Messaging Systems are the backbone of modern, scalable applications. They solve the inefficiencies of traditional RPC-based systems, enabling asynchronous, fault-tolerant communication. Whether you’re building microservices, event-driven systems, or large-scale distributed applications, EMS is an essential tool in your toolbox.</p><p>But wait, there’s more! In an upcoming article, I’ll dive deeper into <strong>Apache Pulsar </strong>how it works, what sets it apart, and why it’s gaining popularity in the EMS world. Keep an eye out for that, you don’t want to miss it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93054cfb8fb4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>