Hi, Apologies if I am posting this in the wrong forum (have just stared with AWS - though might get a better response here given that Camel supports SQS)
I am analyzing the various components of AWS. My current architecture looks similar to the image in the below link http://activemq.2283324.n4.nabble.com/ActiveMQ-Clustered-JBoss-and-JDBC-Master-Slave-td2348023.html;cid=1376917391007-7#a2348028 Components involved: 1. Jboss AS + ActiveMQ (integrated into JBoss) 2. Apache Camel 3. Oracle DB I am using ActiveMQ as messageBroker. My system send/receive external systems via Webservice/JMS. My initial idea is to move this entire system to a EC2 instance and trial it out. I can understand that the following AWS components come into picture 1. Route 53 (for DNS) 2. EC2 instance (where I plan to 'host' my application - to start with I am planning to run the Database and Jboss in the same instance) 3. Amazon S3 (for storing logs/static data) I am trying to understand if Amazon SQS will fit into this at all? My current architecture itself uses a MessageBus (which also does a DB persistance/stire) which ensures reliable availablity of messages. Assuming I do clustering and I have multiple EC2s running - I do have HA. So do I really need to use Amazon SQS here? I can understand it provides a messaging framework - but does it really provide any value in my architecture. regards D -- View this message in context: http://camel.465427.n5.nabble.com/When-to-use-AWS-SQS-tp5737514.html Sent from the Camel - Users mailing list archive at Nabble.com.
