<?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>SQS on {O}</title>
    <link>https://omarmakled.com/tags/sqs/</link>
    <description>Recent content in SQS on {O}</description>
    <generator>Hugo -- 0.151.1</generator>
    <language>en-us</language>
    <atom:link href="https://omarmakled.com/tags/sqs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Serverless Messaging with AWS SAM: SNS, SQS, and Lambda</title>
      <link>https://omarmakled.com/posts/sam-sns-sqs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://omarmakled.com/posts/sam-sns-sqs/</guid>
      <description>&lt;p&gt;This example shows how to build a &lt;strong&gt;serverless messaging pipeline&lt;/strong&gt; using &lt;strong&gt;AWS SAM&lt;/strong&gt;. The project uses &lt;strong&gt;SNS&lt;/strong&gt; to publish messages, &lt;strong&gt;SQS&lt;/strong&gt; queues to separate concerns, and &lt;strong&gt;Lambda functions&lt;/strong&gt; to process the data. It also uses &lt;strong&gt;filter policies&lt;/strong&gt; to control message delivery to each queue.&lt;/p&gt;
&lt;p&gt;This architecture is useful when you want to send different types of data to different consumers, and keep your application components decoupled.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&#34;project-structure&#34;&gt;Project Structure&lt;/h3&gt;
&lt;p&gt;The template defines:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
