You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by boday <be...@initekconsulting.com> on 2013/06/17 19:18:24 UTC

camel deployment options...

I have a complex/high volume (1k msgs/s) Camel application running in
ActiveMQ that I need to scale up (2-5x traffic).  To date, we scaled by
adding more AMQ/Camel VMs and partitioned traffic to each broker.  My
thought is that decoupling Camel from AMQ and adding nodes independently is
a better way to scale horizontally and adds flexibility/reliability to the
architecture...

Assuming this, the question becomes what container to use for the Camel
apps.  I've used both Karaf and Tomcat in the past, but am curious what
others are doing these days in this regard.  Karaf is undoubtedly the better
choice in terms of flexibility, but I tend to fallback to Tomcat because its
a simpler migration path/learning curve for my client (which is a factor).  

Any thoughts on this architecture/deployment model?



-----
Ben O'Day
IT Consultant -http://consulting-notes.com

--
View this message in context: http://camel.465427.n5.nabble.com/camel-deployment-options-tp5734266.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel deployment options...

Posted by Christian Müller <ch...@gmail.com>.
Hi Ben!

I hope you are doing good. We missed you at CamelOne in Boston...

I would recommend Tomcat, if:
- you don't have to support updating individual bundles at run time without
to have a downtime of the entire application (of course it doesn't work if
you provide a JAX-WS, JAX-RS, ... interface in this bundle)
- you don't have to deploy multiple services into a single Tomcat (bigger
deployments)
- you don't use cellar/fabric (I'm not sure, but I don't think they work in
Tomcat - we don't use it)

Otherwise (as we do it), use Karaf or ServiceMix.

My 0,02 €,

Christian Müller
-----------------

Software Integration Specialist

Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html

https://www.linkedin.com/pub/christian-mueller/11/551/642


On Mon, Jun 17, 2013 at 7:18 PM, boday <be...@initekconsulting.com>wrote:

> I have a complex/high volume (1k msgs/s) Camel application running in
> ActiveMQ that I need to scale up (2-5x traffic).  To date, we scaled by
> adding more AMQ/Camel VMs and partitioned traffic to each broker.  My
> thought is that decoupling Camel from AMQ and adding nodes independently is
> a better way to scale horizontally and adds flexibility/reliability to the
> architecture...
>
> Assuming this, the question becomes what container to use for the Camel
> apps.  I've used both Karaf and Tomcat in the past, but am curious what
> others are doing these days in this regard.  Karaf is undoubtedly the
> better
> choice in terms of flexibility, but I tend to fallback to Tomcat because
> its
> a simpler migration path/learning curve for my client (which is a factor).
>
> Any thoughts on this architecture/deployment model?
>
>
>
> -----
> Ben O'Day
> IT Consultant -http://consulting-notes.com
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/camel-deployment-options-tp5734266.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>