Mahesh Mallikarjunaiah ↗️’s Post

Pub/Sub and queue look the same when you hear it for the first time.😱 Here is a simple explanation of what they are and the differences between them. In the illustration depicted below, 🔴 Messaging Queue: People come to the mall to shop. Before they check out, they must wait in the queue to complete the payment. Here, the mall is like a producer, producing people ( who have shopped and are ready to complete payment) who are sent to the queue to complete the payment. One by one, each person completes payment at the checkout counter. The checkout counter is like a consumer. As the queue grows ( more people join the line), more than one checkout ( one consumer ) is needed, and we will need to add more checkout counters ( more consumers). We have Producers, Queues, and Consumers. 🔴 Pub / Sub - Extending on the above example, after the checkout is completed, this customer data might be required by various services. For instance, in the image below, we have a real-time service that calculates how many people have completed the checkout. Hence, the checkout service has subscribed to receive this data. Likewise, marketing and inventory services might subscribe to receive this data. We have Producers, Topics, and Subscribers. 𝗣𝘂𝗯/𝘀𝘂𝗯:⏹️ The subscribers don’t have to reveal anything to the publishers. Messages are in the topic even after multiple subscribers consume it. Messages are sent to multiple subscribers simultaneously and asynchronously Message ordering and sending to various consumers is not guaranteed Producers and consumers have loose coupling 𝗤𝘂𝗲𝘂𝗲: ⏹️ Queues need to reveal who they are sending messages to Producers would put the messages in the queue, storing them until one of the consumers consumes them Producers put the messages in the queue, typically sent using some ordering and sequentially to a single receiver Message ordering and sending to consumers is guaranteed Producers and consumers have some sort of relationship #engineering #systemdesign #interview #productdevelopment #eventdrivenarchitecture

Pub/Sub and queue look the same when you hear it for the first time.😱 Here is a simple explanation of what they are and the differences between them. In the illustration depicted below, 🔴 Messaging Queue: People come to the mall to shop. Before they check out, they must wait in the queue to complete the payment. Here, the mall is like a producer, producing people ( who have shopped and are ready to complete payment) who are sent to the queue to complete the payment. One by one, each person completes payment at the checkout counter. The checkout counter is like a consumer. As the queue grows ( more people join the line), more than one checkout ( one consumer ) is needed, and we will need to add more checkout counters ( more consumers). We have Producers, Queues, and Consumers. 🔴 Pub / Sub - Extending on the above example, after the checkout is completed, this customer data might be required by various services. For instance, in the image below, we have a real-time service that calculates how many people have completed the checkout. Hence, the checkout service has subscribed to receive this data. Likewise, marketing and inventory services might subscribe to receive this data. We have Producers, Topics, and Subscribers. 𝗣𝘂𝗯/𝘀𝘂𝗯:⏹️ The subscribers don’t have to reveal anything to the publishers. Messages are in the topic even after multiple subscribers consume it. Messages are sent to multiple subscribers simultaneously and asynchronously Message ordering and sending to various consumers is not guaranteed Producers and consumers have loose coupling 𝗤𝘂𝗲𝘂𝗲: ⏹️ Queues need to reveal who they are sending messages to Producers would put the messages in the queue, storing them until one of the consumers consumes them Producers put the messages in the queue, typically sent using some ordering and sequentially to a single receiver Message ordering and sending to consumers is guaranteed Producers and consumers have some sort of relationship #engineering #systemdesign #interview #productdevelopment #eventdrivenarchitecture

Pub/Sub and queue look the same when you hear it for the first time.😱 Here is a simple explanation of what they are and the differences between them. In the image depicted below, 🔴 Messaging Queue: People come to the mall to shop. Before they check out, they must wait in the queue to complete the payment. Here, the mall is like a producer, producing people ( who have shopped and are ready to complete payment) who are sent to the queue to complete the payment. One by one, each person completes payment at the checkout counter. The checkout counter is like a consumer. As the queue grows ( more people join the line), more than one checkout ( one consumer ) is needed, and we will need to add more checkout counters ( more consumers). We have Producers, Queues, and Consumers. 🔴 Pub / Sub - Extending on the above example, after the checkout is completed, this customer data might be required by various services. For instance, in the image below, we have a real-time service that calculates how many people have completed the checkout. Hence, the checkout service has subscribed to receive this data. Likewise, marketing and inventory services might subscribe to receive this data. We have Producers, Topics, and Subscribers. #engineering #systemdesign #interview #productdevelopment #eventdrivenarchitecture

Title: Navigating Pub/Sub and Queues in Distributed Systems In distributed systems, getting messages where they need to go efficiently is key. Here's a quick guide to Pub/Sub and Queues, two ways to do just that. Pub/Sub (Publish/Subscribe) How it Works: Think of it like a radio broadcast. Publishers send messages out to topics, and subscribers tune in to get those messages. Why it's Handy: Great for real-time updates and events. It keeps systems flexible and can handle lots of users at once. When to Use It: Perfect for things like real-time analytics, event-driven setups, and IoT networks. Queues How it Works: Picture a line at a coffee shop. Messages get in line, and consumers take them out one by one. Why it's Handy: Ensures messages are processed in order and only once. Plus, it's reliable and great for balancing workloads. When to Use It: Ideal for task distribution, handling big workloads, and making sure every message gets where it needs to go. Wrap-Up Understanding Pub/Sub and Queues helps you pick the right tool for the job when building distributed systems. Pub/Sub keeps things flexible and real-time, while Queues ensure reliability and orderly processing. #DistributedSystems #MessagingPattern #PubSub #Queues #RealTimeMessaging #EventDrivenArchitecture #IoTNetworks #TaskDistribution #WorkloadBalancing #TechArchitecture

🎉 Exciting news! Cartconvert.co is now live and we cannot wait to speak with you. Have a look at our brand new website and book a demo with Owen to see our powerful checkout recovery platform! #Ecommerce #RetailTech #CartConvert #CustomerExperience #BusinessGrowth

🚀 Exciting News: I'm thrilled to announce the launch of my company, CartConvert!   A powerful tool aimed at tackling one of the biggest challenges in online retail: abandoned checkouts. Built with my former colleagues from Moltin (Acquired by Elastic Path) / Elastic Path, shoutout to Evgenia Williamson and Kate, as well as my former brand customer turned dear friend / eComm legend Ann Marie Cardinale, CartConvert helps brands significantly lower their abandoned checkout rates and drive incremental revenue growth through peer to peer messaging. Having a team that has worked in multiple facets of the shopper journey throughout our careers, we set out to solve the checkout conversion problem brands experience on a daily basis without having them throw more money at an unproven solution. Here's how CartConvert is making a difference: 🌟 Advanced Recovery Strategies: By leveraging sophisticated algorithms, CartConvert identifies and targets potential customers who abandon their carts, ensuring timely reminders and incentives to complete their purchases through the use of live support agents. 🔍 Behavioral Insights: Gain deep insights into customer behavior with detailed analytics and reporting. Understand exactly where in the checkout process customers are dropping off and optimize your strategies accordingly. 💬 Personalized Messaging: Engage customers outside of your marketing network with personalized messages and offers tailored to their browsing history and preferences, increasing the likelihood of conversion.  📈 Incremental Revenue Lift: Through effective recovery of abandoned carts and enhanced customer engagement, CartConvert not only reduces lost sales but also drives additional revenue that would have otherwise been missed from your current email / sms marketing automations. And we only get paid when we recover that abandoned checkout for you. Whether you're a small boutique or a large enterprise, CartConvert is designed to scale with your business needs, providing a seamless integration into your existing e-commerce platform. Join us in transforming the way brands recover sales and enhance customer experiences. Visit CartConvert.co to learn more about our innovative solution or feel free to give me a shout to catch up! Let's convert abandoned checkouts into delighted customers and sustainable growth together! #Ecommerce #RetailTech #CartConvert #CustomerExperience #BusinessGrowth

Bring checkout to shoppers, not shoppers to checkout! 🛒  Our VP of Marketing and Tech Partnerships, Casey Gannon, shared insights with Chain Store Age on how retailers can transform the shopping experience with a Checkout Anywhere approach. From search engines to shoppable photos, emails, SMS, and blogs, embedding checkout directly where customers discover products creates a seamless, instant path to purchase. As Casey puts it, “Checkout doesn’t have to be the final touchpoint—it can be the first and only step.” Curious how this strategy eliminates friction and boosts conversions? Read the full article here: https://lnkd.in/g96yNuCd

Here's some recent news from SIRL about shopper traffic insights and in-store retail media activation - delivering the right message at the right time at the right place!

This article explores how providing online customers with information about high-stock delivery windows can reduce stockouts and increase customer spending. An experiment conducted by Instacart showed that this approach led to a 4.6% increase in average daily spending and a decrease in the proportion of items replaced or refunded. The study highlights the broader applicability of this strategy for various online retailers and its potential to improve customer experience and revenue.

Checkout SIRL's latest feature, the In-Store Customer Journey view illustrating how customers are shopping before and after making their purchasing decisions. Our CTO Bart Shappee explains the capabilities of this view and covers example use cases such as optimizing #retailmedia placement on the floor. Comment below with your own ideas on how this data can be used to improve your customer's in-store experience. #rtls