Amazon SQS
Point-Point vs Publish-Subscribe: Supports only Point-Point model. No PubSub.
Messages are not guaranteed to be delivered in FIFO order.
Messages can be requested in batches with a max batch size of 10 messages.
message consumption by the consumers is not real time due to polling interval.
every request to SQS would incur some cost (1$ for 1million requests).
http://ift.tt/1OVubEn
That’s sent or received, so really it’s 2 bucks a million. Another thing with SQS: it’s slow.
As a result of at-least-once delivery, consuming services need to make sure that re-processing of messages does not result in an inconsistent state of the system by handling the messages in an idempotent manner.
Point-Point vs Publish-Subscribe: Supports only Point-Point model. No PubSub.
Messages are not guaranteed to be delivered in FIFO order.
Messages can be requested in batches with a max batch size of 10 messages.
message consumption by the consumers is not real time due to polling interval.
every request to SQS would incur some cost (1$ for 1million requests).
http://ift.tt/1OVubEn
That’s sent or received, so really it’s 2 bucks a million. Another thing with SQS: it’s slow.
As a result of at-least-once delivery, consuming services need to make sure that re-processing of messages does not result in an inconsistent state of the system by handling the messages in an idempotent manner.
from Public RSS-Feed of Jeffery yuan. Created with the PIXELMECHANICS 'GPlusRSS-Webtool' at http://gplusrss.com http://ift.tt/1bYyc97
via LifeLong Community
No comments:
Post a Comment