amazon-sqs

问题 I'm running Laravel 5.3. I'm attempting to test a queue job, and I have my queue configured to use Amazon SQS. My app is able to push a job onto the queue, and I can see the job in SQS. But it stays there, never being processed. I've tried running php artisan queue:work , queue:listen , queue:work sqs ... None of them are popping the job off the queue. I'm testing this locally with Homestead. Is there a trick to processing jobs from SQS? 回答1: I faced the same problem. I was using supervisor.

问题 Is it possible to send a messaging request to Amazon's SQS directly from javascript? I'm trying to create a logging system and would love to bypass sending the request to a middleman server. Also, does anybody know of any alternatives to this solution that I may leverage? 回答1: SQS(and as a matter of fact all aws services) expose REST based apis. You can directly make a http request to the SQS REST api through javascript code. The api documentation id given here. 回答2: Unless you load your

问题 I have a process that creates SQS messages and places them on an SQS queue and another process that reads those messages and performs certain logic based on the contents of the body and attributes of the message. I can successfully create a message on the SQS queue with body and attributes, but I have a problem when reading the message attributes back! I am sure my message creation process is correct, I can see the attributes in the AWS SQS console for the queue. I just cannot figure out why

问题 I seem to be stuck at sending the compressed messages from PHP to NodeJS over Amazon SQS. Over on the PHP side I have: $SQS->sendMessage(Array( 'QueueUrl' => $queueUrl, 'MessageBody' => 'article', 'MessageAttributes' => Array( 'json' => Array( 'BinaryValue' => bzcompress(json_encode(Array('type'=>'article','data'=>$vijest))), 'DataType' => 'Binary' ) ) )); NOTE 1: I also tried putting compressed data directly in the message, but the library gave me an error with some invalid byte data On the

问题 I am currently struggle to find a solution for implement a specific kind of queue, which require the following traits: All queue must respect the order that job were added. The whole queue will have a concurrency of 1, which means that there will only be one job execute at a time per queue , not worker. There will be more than a few thousand queue like this. It need to be distributed and be able to scale (example if I add a worker) Basically it is a single process FIFO queue, and this is

问题 I'm trying to understand whether I need SQS in my workflow if someone can help explain. In my app, when an action is taken, it submits info to SNS topic which invokes LAMBDA to do some processing. This is working great as it is. When I do research online, it seems that people are using SQS in this stack as well where SNS would put info on SQS and then SQS would then invoke LAMBDA. I guess what I'm trying to understand is the need for SQS in this. What value doe that add or in other words,

问题 On my site I'd like to do push notifications of comments like Stackoverflow does. Amazon SNS/SQS seems to provide a framework to do this but I'm having difficulty finding any code/explanation on the web for anything beyond a "hello world" equivalent. From reading the AWS SNS/SQS documentation it looks like I need the following: logic: post comment/answer to a new question create topic (for first comment/answer only) publish message subscribe to topic PHP on the page where comments are posted

问题 I know that it is possible to consume a SQS queue using multiple threads. I would like to guarantee that each message will be consumed once. I know that it is possible to change the visibility timeout of a message, e.g., equal to my processing time. If my process spend more time than the visibility timeout (e.g. a slow connection) other thread can consume the same message. What is the best approach to guarantee that a message will be processed once? 回答1: What is the best approach to guarantee

问题 I know that it is possible to consume a SQS queue using multiple threads. I would like to guarantee that each message will be consumed once. I know that it is possible to change the visibility timeout of a message, e.g., equal to my processing time. If my process spend more time than the visibility timeout (e.g. a slow connection) other thread can consume the same message. What is the best approach to guarantee that a message will be processed once? 回答1: What is the best approach to guarantee

问题 I have an architecture which looks like as follows:- Multiple SNS -> (AWS Lambda or SQS with Poller)??? -> Dynamo Db So, basically multiple SNS have subscribed to AWS Lambda or SQS with Poller and that thing pushes data to Dynamo Db. But this ? thing do lot of transformation of message in between. So, now for such case, I can either use AWS Lambda or SQS with Poller. With AWS Lambda, I can do transformation in Lambda function and with SQS with Poller, I can do transformation in Poller. With