camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem jiang <>
Subject Re: When to use AWS SQS?
Date Mon, 19 Aug 2013 14:22:24 GMT

I think you should know the difference between the IAAS and SAAS[1].

When you using EC2, you don't need to take care of the physical machine any more, but you
still need to install the OS, DB and Application Server to build up your service.
But if you are using AWS SQS, you don't need take care of the physical machine, Broker, or
DB, you just need to use SQS API to access the service that you want.  
And AWS SQS will solve the HA, scalability issue for you.

Willem Jiang

Red Hat, Inc.
Blog: ( (English)
 ( (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem

On Monday, August 19, 2013 at 10:05 PM, deepak_a wrote:

> 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
> 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:
> Sent from the Camel - Users mailing list archive at (

View raw message