Another thing to consider is that SQS is great for some situations, but consider these facts:
Message size cannot be greater than 256K Messages are not delivered in order Your throughput and latency requirements (need to be fast?) need to be considered.. On Mon, Aug 19, 2013 at 8:11 AM, deepak_a <angesh...@gmail.com> wrote: > Hi, > > Thanks, that was useful. > We are providing our Software as a Saas. > > Its sometimes hosted/deployed within our firm and at times deployed at the > client's site. > Now we plan to deploy our software in the cloud and provide it as a service > to clients. > > I am still trying to understand if there is any "value" in using AWS SQS. > As mentioned - we are able to achieve HA & HS using current architecture - > so trying to understand if there is any value in using AWS SQS. (in which > case my architecture will change a lot to use SQS) > > regards > D > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/When-to-use-AWS-SQS-tp5737514p5737518.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
