--- title: Day 22/30: Not every task must happen immediately description: Explains how Amazon SQS lets applications decouple work by placing messages in a queue instead of processing everything synchronously, reducing tight... canonical: https://daily.dev/posts/day-22-30-not-every-task-must-happen-immediately-yy15r71p4 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Day 22/30: Not every task must happen immediately | daily.dev og:description: Explains how Amazon SQS lets applications decouple work by placing messages in a queue instead of processing everything synchronously, reducing tight... og:url: https://daily.dev/posts/day-22-30-not-every-task-must-happen-immediately-yy15r71p4 og:image: https://api.daily.dev/og/posts/yY15R71p4.png og:image:alt: Day 22/30: Not every task must happen immediately og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Day 22/30: Not every task must happen immediately **[Ezile Mdodana](https://daily.dev/sources/7vb9selrkhohgnzepmfvq)** · [@ezilemdodana](https://daily.dev/ezilemdodana) · 1 min read · 3 upvotes · 0 comments ## Summary Explains how Amazon SQS lets applications decouple work by placing messages in a queue instead of processing everything synchronously, reducing tight dependencies between services and helping systems absorb traffic spikes. Uses an online shop example where order confirmation, invoicing, email, and stock updates don't all need to complete before the customer gets a response. ## Content Imagine an online shop where every order must wait for the invoice, email and stock update to finish before the customer receives confirmation. One slow process delays everything. Amazon SQS allows applications to place messages in a queue for other components to process independently. This reduces tight dependencies and helps systems handle traffic spikes. A queue is the application saying: “I received the work. I will process it properly.” Much healthier than everyone shouting at every service simultaneously. #AWSWithoutTheFluff #AmazonSQS #CloudArchitecture ## Similar posts on daily.dev - [How to Scale Long-Running API Requests](https://daily.dev/posts/how-to-scale-long-running-api-requests-aj4mhj66o) · Milan Jovanović · 57 upvotes · 3 comments - [Amazon SQS turns 20: Two decades of reliable messaging at scale](https://daily.dev/posts/amazon-sqs-turns-20-two-decades-of-reliable-messaging-at-scale-eor4p7rmi) · AWS · 1 upvotes · 0 comments - [I Added SQS to My Backend :\)](https://daily.dev/posts/i-added-sqs-to-my-backend--bnqclheep) · Medium · 0 upvotes · 0 comments - [Amazon Connect Customer now supports scheduling tasks up to 90 days in advance](https://daily.dev/posts/amazon-connect-customer-now-supports-scheduling-tasks-up-to-90-days-in-advance-ivxf0nnro) · AWS · 0 upvotes · 0 comments --- Tags: [#aws](https://daily.dev/tags/aws), [#architecture](https://daily.dev/tags/architecture), [#distributed-systems](https://daily.dev/tags/distributed-systems) [View this post on daily.dev](https://daily.dev/posts/day-22-30-not-every-task-must-happen-immediately-yy15r71p4) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"DiscussionForumPosting","mainEntityOfPage":"https://daily.dev/posts/day-22-30-not-every-task-must-happen-immediately-yy15r71p4","headline":"Day 22/30: Not every task must happen immediately","text":"Explains how Amazon SQS lets applications decouple work by placing messages in a queue instead of processing everything synchronously, reducing tight dependencies between services and helping systems absorb traffic spikes. Uses an online shop example where order confirmation, invoicing, email, and stock updates don't all need to complete before the customer gets a response.","url":"https://daily.dev/posts/day-22-30-not-every-task-must-happen-immediately-yy15r71p4","datePublished":"2026-08-19T06:56:06.216Z","dateModified":"2026-09-13T21:34:16.018Z","author":{"@type":"Person","name":"Ezile Mdodana","url":"https://daily.dev/ezilemdodana","image":"https://media.daily.dev/image/upload/s--1OI8gwnO--/f_auto/v1771923757/avatars/avatar_7vB9SeLRKhOHGnzEpmFvQ?_a=BAMAMiiu0","description":"Software Project Lead sharing practical insights on NestJS, Angular, AWS and scalable systems.","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":8430}},"image":"https://media.daily.dev/image/upload/s--Fdf5A_fK--/f_auto/v1787122567/posts/yY15R71p4?_a=BAMAMicg0","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":3},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"isPartOf":{"@type":"WebPage","url":"https://daily.dev/sources/7vb9selrkhohgnzepmfvq","name":"Ezile Mdodana"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Ezile Mdodana","item":"https://daily.dev/sources/7vb9selrkhohgnzepmfvq"},{"@type":"ListItem","position":3,"name":"Day 22/30: Not every task must happen immediately"}]} ```