Updated AWS::SQS::QueueInlinePolicy
You can now associate one Amazon SQS policy with one queue.
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-sqs-queueinlinepolicy.html #sqs #cloudformation
This post explores three use-cases and design patterns for handling failures.
#AWS #AWSBlog #Serverless #Cloud #CloudComputing #AmazonWebServices #Lambda #SQS
#aws #awsblog #serverless #Cloud #CloudComputing #AmazonWebServices #lambda #SQS
Lambda + SQS Users Should Know About This
Woot.. completed the RabbitMQ course with CloudAMQP. I will blog about the #tech later today on https://maolte.ie. On the #course. Well done and thank you to CloudAMQP for putting together a good (and free) course on this #message broker. My production experience with #aws #sqs (managed broker by #aws) will feature in my upcoming blog so stay tuned for forthcoming updates on this, #demo #projects plus more... #cloudinfrastructure #cloud #cloudarchitecture
#tech #course #message #aws #SQS #demo #projects #cloudinfrastructure #cloud #cloudarchitecture
AWS Lambda Now Supports Maximum Concurrency for SQS as Event Source
My recap for @infoq
#aws #sqs #serverless
https://www.infoq.com/news/2023/01/aws-lambda-sqs-concurrency/
Currently, no observability services can track #eventbrige or a chain like #apigw to #sns to #sqs. Pipes' arrival makes it even worse. I am happy about #cloudwatch EMF. It is overall cheaper than paying third-party services, and I can track all I want.
I do not have a nice ServiceMap, but I have all I need for a dashboard.
#eventbrige #apigw #sns #SQS #cloudwatch #aws #serverless #EDA
The #eda part is made of:
#APIGW to #SNS or #EventBridge to #SQS to #lambda
Still checking, but the response from Lambda to the user with IoT looks slower, not by much when you are using SNS than Sync operation. When I use EventBridge, it is kind of a second later.
The power of #serverless
#EDA #apigw #sns #eventbridge #SQS #lambda #serverless
Moving from synchronous #apigw to fat #lambda that calls in parallel #eventbridge #dynamodb #s3 #stepfunctions #sqs #sns to fully #eda lambda that calls just #dynamodb and fan-out with #sns gave me just an 8% (p99) increase in term of scalability. #eda with #eventbridge is the same as the fatty ðŸ˜
#apigw #lambda #eventbridge #dynamodb #s3 #stepfunctions #SQS #sns #EDA
Finally...
AWS X-Ray adds trace linking for event-driven applications built on Amazon SQS and AWS Lambda
https://aws.amazon.com/about-aws/whats-new/2022/11/aws-x-ray-trace-linking-event-driven-applications-amazon-sqs-lambda/
#aws #tracing #serverless #lambda #sqs #observability
#aws #tracing #serverless #lambda #SQS #observability
Why #SQS and Simple Workflow Services were among the first AWS services released? Read the "distributed computing manifesto": the 1998 document that drove the re-architecture of http://amazon.com to micro services and asynchronous workflows.
https://www.allthingsdistributed.com/2022/11/amazon-1998-distributed-computing-manifesto.html
@solnic That's interesting. We're on #Rails and see much lower memory usage on most workers, which I've attributed to them generally only executing quite a small set of code. Our web dyno generally runs up to 5GB of memory, but a worker that runs constantly only polling an #SQS queue and writing messages to #PostgreSQL uses 300MB.