<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Application Integration on 🏠</title><link>https://tofl.github.io/docs/5-application-integration-sqs-sns-eventbridge-kinesis-step-functions/</link><description>Recent content in Application Integration on 🏠</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://tofl.github.io/docs/5-application-integration-sqs-sns-eventbridge-kinesis-step-functions/index.xml" rel="self" type="application/rss+xml"/><item><title>11. Error Handling &amp; Retry Patterns</title><link>https://tofl.github.io/docs/5-application-integration-sqs-sns-eventbridge-kinesis-step-functions/error-handling-retry-patterns/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tofl.github.io/docs/5-application-integration-sqs-sns-eventbridge-kinesis-step-functions/error-handling-retry-patterns/</guid><description>&lt;h2 id="error-handling--retry-patterns--cross-cutting-theme"&gt;Error Handling &amp;amp; Retry Patterns — Cross-Cutting Theme&lt;a class="anchor" href="#error-handling--retry-patterns--cross-cutting-theme"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Before diving into individual services, it&amp;rsquo;s worth internalizing a set of patterns that appear repeatedly across SQS, SNS, Lambda, API Gateway, DynamoDB, Kinesis, Step Functions, and EventBridge. The exam tests these concepts in context — meaning you&amp;rsquo;ll see them embedded in scenario questions about specific services — so understanding them as a unified mental model first will save you significant effort later.&lt;/p&gt;</description></item><item><title>12. SQS</title><link>https://tofl.github.io/docs/5-application-integration-sqs-sns-eventbridge-kinesis-step-functions/sqs/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tofl.github.io/docs/5-application-integration-sqs-sns-eventbridge-kinesis-step-functions/sqs/</guid><description>&lt;h2 id="sqs-simple-queue-service"&gt;SQS (Simple Queue Service)&lt;a class="anchor" href="#sqs-simple-queue-service"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Amazon Simple Queue Service (SQS) is a fully managed message queuing service that lets you decouple the components of a distributed application. The core problem it solves is &lt;strong&gt;temporal coupling&lt;/strong&gt;: without a queue, if a downstream service (consumer) is slow, overloaded, or temporarily unavailable, the upstream service (producer) either fails or has to wait. SQS breaks that dependency — producers drop messages into the queue and move on, consumers process at their own pace. &lt;a href="https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/welcome.html"&gt;🔗&lt;/a&gt;&lt;/p&gt;</description></item><item><title>13. SNS</title><link>https://tofl.github.io/docs/5-application-integration-sqs-sns-eventbridge-kinesis-step-functions/sns/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tofl.github.io/docs/5-application-integration-sqs-sns-eventbridge-kinesis-step-functions/sns/</guid><description>&lt;h2 id="sns-simple-notification-service"&gt;SNS (Simple Notification Service)&lt;a class="anchor" href="#sns-simple-notification-service"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Amazon Simple Notification Service (SNS) &lt;a href="https://docs.aws.amazon.com/sns/latest/dg/welcome.html"&gt;🔗&lt;/a&gt; is a fully managed pub/sub messaging service. Where SQS decouples a single producer from a single consumer, SNS solves a different problem: &lt;strong&gt;broadcasting one message to many recipients simultaneously&lt;/strong&gt;. A single &lt;code&gt;Publish&lt;/code&gt; call to an SNS topic can trigger an email notification, invoke a Lambda function, and drop a copy of the message into an SQS queue — all at once. This makes SNS the natural choice for fan-out architectures and alert pipelines.&lt;/p&gt;</description></item><item><title>14. EventBridge</title><link>https://tofl.github.io/docs/5-application-integration-sqs-sns-eventbridge-kinesis-step-functions/eventbridge/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tofl.github.io/docs/5-application-integration-sqs-sns-eventbridge-kinesis-step-functions/eventbridge/</guid><description>&lt;h2 id="eventbridge"&gt;EventBridge&lt;a class="anchor" href="#eventbridge"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Amazon EventBridge is a serverless event bus that connects AWS services, your own applications, and third-party SaaS platforms by routing events from producers to consumers based on rules you define. It exists to solve a fundamental integration problem: how do you let dozens of services react to things that happen in your system without coupling them together? Before EventBridge, you&amp;rsquo;d wire services directly — Lambda calls SQS, SQS triggers Lambda, Lambda calls another Lambda — creating brittle chains that are hard to change and harder to debug. EventBridge inverts this: producers emit events onto a bus, and any number of consumers subscribe to exactly the events they care about. Neither side knows about the other.&lt;/p&gt;</description></item><item><title>15. Kinesis Data Streams</title><link>https://tofl.github.io/docs/5-application-integration-sqs-sns-eventbridge-kinesis-step-functions/kinesis-data-streams/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tofl.github.io/docs/5-application-integration-sqs-sns-eventbridge-kinesis-step-functions/kinesis-data-streams/</guid><description>&lt;h2 id="kinesis-data-streams"&gt;Kinesis Data Streams&lt;a class="anchor" href="#kinesis-data-streams"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Modern applications often generate data faster than any single consumer can process it — user clickstreams, IoT sensor readings, application logs, financial transactions. Amazon Kinesis Data Streams &lt;a href="https://docs.aws.amazon.com/streams/latest/dev/introduction.html"&gt;🔗&lt;/a&gt; exists to solve exactly this problem: it lets you ingest large volumes of real-time data, durably store it, and allow one or more consumers to process it independently at their own pace. Unlike SQS, where a message is consumed and gone, Kinesis retains records in order for a configurable window, making it ideal for replay, auditing, and parallel processing by multiple consumers.&lt;/p&gt;</description></item><item><title>16. Step Functions</title><link>https://tofl.github.io/docs/5-application-integration-sqs-sns-eventbridge-kinesis-step-functions/step-functions/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tofl.github.io/docs/5-application-integration-sqs-sns-eventbridge-kinesis-step-functions/step-functions/</guid><description>&lt;h2 id="step-functions"&gt;Step Functions&lt;a class="anchor" href="#step-functions"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Modern applications rarely do just one thing — they chain together multiple operations: validate input, write to a database, call an external API, send a notification, and handle failures at each step. The naive approach is to wire these steps together inside Lambda functions, where one function calls another and so on. This creates tightly coupled, fragile chains that are hard to debug, retry, or modify. AWS Step Functions solves this by letting you define your workflow as a &lt;strong&gt;state machine&lt;/strong&gt; — a visual, auditable graph of steps and transitions that AWS manages for you. You describe &lt;em&gt;what&lt;/em&gt; should happen and &lt;em&gt;in what order&lt;/em&gt;; Step Functions handles the execution, retries, error handling, and state passing between steps. &lt;a href="https://docs.aws.amazon.com/step-functions/latest/dg/welcome.html"&gt;🔗&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>