<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Integration on Daman Arora</title>
    <link>https://damanarora.netlify.app/tags/integration/</link>
    <description>Recent content in Integration on Daman Arora</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Sun, 17 May 2026 22:00:00 +0000</lastBuildDate><atom:link href="https://damanarora.netlify.app/tags/integration/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AWS Messaging: SQS, SNS, Kinesis, and Amazon MQ</title>
      <link>https://damanarora.netlify.app/posts/aws-messaging-sqs-sns-kinesis-mq/</link>
      <pubDate>Sun, 17 May 2026 22:00:00 +0000</pubDate>
      
      <guid>https://damanarora.netlify.app/posts/aws-messaging-sqs-sns-kinesis-mq/</guid>
      <description>Once an app grows past a single service, the pieces need to talk to each other — but you don&amp;rsquo;t want them tightly coupled. AWS&amp;rsquo;s messaging services are the glue: they let one part of your app hand off work or events to another without either side having to know much about the other.
The mental map ┌─────────────────────────────────────────────────────────┐ │ PATTERN 1: One-to-one (queue) │ │ • SQS (producer → queue → one consumer) │ ├─────────────────────────────────────────────────────────┤ │ PATTERN 2: One-to-many (pub/sub) │ │ • SNS (publisher → topic → many subscribers) │ ├─────────────────────────────────────────────────────────┤ │ PATTERN 3: Real-time data streams │ │ • Kinesis (continuous data → process → store) │ ├─────────────────────────────────────────────────────────┤ │ PATTERN 4: Industry-standard protocols │ │ • Amazon MQ (managed RabbitMQ/ActiveMQ for migration)│ └─────────────────────────────────────────────────────────┘ SQS — Simple Queue Service SQS is a managed message queue.</description>
    </item>
    
  </channel>
</rss>
