blocks|key|4139076|text|无序消息传递是SQS设计中固有的特性。您可以尝试通过对消息进行编号并在本地存储无序的消息，直到丢失的消息到达，来解决这个问题，但这可能不值得这么麻烦。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4139077|SQS真的有点奇怪，它做到了它所说的，但它所做的并不是大多数人在消息总线中寻找的。我真的希望亚马逊能提供更多像RabbitMQ一样的排队解决方案。SQS实际上只适合分布那些甚至不是远程耦合的任务，以及顺序和延迟等并不重要的任务。例如，它非常适合于将已完成的订单发送到发货中心，或者安排打印作业。|4139078|他们自己的文档显示它被用来计划缩略图的创建，但当我最近将其用于这个确切的目的时，我很快发现我的用户不会对延迟印象深刻:有时是30-50秒。|4139079|您仍然可以在EC2节点上运行RabbitMQ，尽管其可伸缩性不如SQS，但它确实是集群的，应该会让您走得更远。|4139080|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Unordered message delivery is inherent in the design of SQS. You could try to work around it by numbering the messages and storing the out-of-order messages locally until the missing messages arrive, but its probably not worth the hassle.

SQS is really a bit of an odd duck, it does what it says, but what it does isn't what most people are looking for in a message bus. I really wish Amazon would offer and additional queuing solution more like RabbitMQ. SQS is really only suited for distributing tasks that aren't even remotely coupled, and where things like order and latency aren't important. For instance it would be great for sending completed orders to a shipping center, or perhaps scheduling print jobs.

Their own documentation shows it being used to schedule thumbnail creation, but when I recently used it for this exact purpose I quickly discovered that my users weren't going to be impressed with the latency: which at times is 30-50 seconds. 

You can still run RabbitMQ on EC2 nodes, and while not as scalable as SQS it does cluster and should take you pretty far.

blocks|key|4139110|text|你可以试试IronMQ。它像SQS一样托管，保证了先进先出排序，没有最终的一致性延迟，具有更高的可扩展性，您可以在几分钟内启动并运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4139111|这里有一个PHP库：https://github.com/iron-io/iron_mq_php|4139112|免责声明:我为Iron.io工作|4139113|entityMap|0|LINK|mutability|MUTABLE|url|http://www.iron.io/products/mq|1|https://github.com/iron-io/iron_mq_php^0|5|6|0|0|A|12|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

You could try <a href="http://www.iron.io/products/mq" rel="nofollow">IronMQ</a>. It is hosted like SQS, has guaranteed first in first out ordering, no eventual consistency delays, is uber scalable and you can be up and running in minutes. 

Here's a PHP library for it: <a href="https://github.com/iron-io/iron_mq_php" rel="nofollow">https://github.com/iron-io/iron_mq_php</a>

Disclaimer: I work for Iron.io

blocks|key|4139138|text|SQS+documentation会为你回答这个问题(我强调粗体直接回答你的问题)：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4139139|4139140|+Amazon+SQS尽最大努力保持消息中的顺序，但由于队列的分布式性质，我们不能保证您将按发送消息的确切顺序接收消息。如果您的系统要求保留顺序，我们建议您在每封邮件中放置排序信息，以便您可以在收到邮件时对邮件重新排序。|blockquote|style|BOLD|4139141|4139142|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/DistributedQueues.html^0|0|H|0|0|0|1O|1E|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|-4|5|6|7|W|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|X|8|@$A|Y|B|Z|H|I]]|9|@]|C|$]]|$1|J|3|-4|5|6|7|10|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

The <a href="http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/DistributedQueues.html" rel="nofollow">SQS documentation</a> answers this for you (bold is my emphasis to directly answer your question): 

<blockquote>
 Amazon SQS makes a best effort to preserve order in messages, but due
 to the distributed nature of the queue, we cannot guarantee you will
 receive messages in the exact order you sent them. If your system
 requires that order be preserved, we recommend you place sequencing
 information in each message so you can reorder the messages upon
 receipt.
</blockquote>

blocks|key|4139186|text|我已经尝试实现FIFO方式，以便以与发送消息相同的顺序接收消息|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4139187|为此，您可以使用每次发送的消息序列号和消息，并在接收端进行验证|4139188|通过使用这种方法，您可以按FIFO顺序获得所需的输出|4139189|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I have tried to implement the FIFO fashion for receiving the messages in the same order they were sent

For this you can use message sequence no which it sent every time with message and validate at the receiver end 

By Using this way you can get desired output in FIFO order

i would like to take messages from amazon sqs in the same order in which it is inserted into sqs ( first in first out model).
Is their any way to implement it??
I am using zend php for programing.

amazon sqs :read message not in order

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我想从amazon sqs中获取消息的顺序与其插入sqs的顺序相同(先入先出模型)。他们有什么办法实现它吗？？我正在使用zend php进行编程。

问amazon sqs :阅读消息顺序不正确
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问amazon sqs :阅读消息顺序不正确EN