You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by contactreji <co...@gmail.com> on 2015/10/14 20:12:54 UTC
Camel Deployment - Best Practice
Hello guys
We deliver integration solutions using Apache Camel with big volumes of data
in production. I was just curious to know what would be the best choice as a
container?
Our integration application contain camel routes extended using RouteBuilder
API and I see we can use Osgi containers like Fuse / Servicemix or web
containers like Tomcat, EAP or use Spring Boots.
What would you all suggest? Any of the above options has any characteristics
which qualifies it as best among the lot or perhaps gives an edge of the
others?
Cheers
Reji
-----
Reji Mathews
Sr. Developer - Middleware Integration / SOA ( Open Source - Apache Camel & Jboss Fuse ESB | Mule ESB )
LinkedIn - http://in.linkedin.com/pub/reji-mathews/31/9a2/40a
Twitter - reji_mathews
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Deployment-Best-Practice-tp5772655.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel Container Deployment - Best Practice
Posted by alexey-s <al...@mail.ru>.
I use a bunch of Apache Karaf and Apache Camel.
At the beginning of the road I used OSGi Blueprint.
Over time, the Blueprint gave up and switched to Dynamic Services.
Spring DS - a type of OSGi Blueprint. It was quite a compelling reason
authors
abandon basic Spring DS in OSGi. This is the main reason for the refusal of
Spring.
Daylight OSGi DS due order to start and stop Camel Contexts, depending on
the OSGi Services.
When using Blueprint, running processes are not stopped.
The process of trying to interact with the modified service hidden behind
Blueprint Proxy. It is not always correct.
OSGi DS stops Camel service, change the basic services and start new
processes.
This is convenient for the loss and restoration of communication between
servers.
As the system works with a database made the choice to MyBatis Guice.
Do not fall for lack of JPA Transaction Manager in a JBoss AS.
Do not work properly annotations transaction management.
Camel (Spring) Transaction very hard to maintain.
The main branch of the project MyBatys implemented the idea of the dynamic
release
resources. This gave a dynamic replacement OSGi Bundles without the need for
stop the server Apache Karaf.
The main branch of the project implemented support for MyBatis Guice
Transaction Manager. Annotations and Camel (Spring) Transaction working
properly.
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Container-Deployment-Best-Practice-tp5772655p5772735.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel Deployment - Best Practice
Posted by Arnaud Deprez <ar...@gmail.com>.
Hi,
If you need/like OSGi, I would go for karaf but if you don't, I'd go for
spring-boot as you can benefit from the whole benefit of spring without
having to deal with specific container configuration.
Rgds,
On Wed, Oct 14, 2015 at 8:13 PM contactreji <co...@gmail.com> wrote:
> Hello guys
>
> We deliver integration solutions using Apache Camel with big volumes of
> data
> in production. I was just curious to know what would be the best choice as
> a
> container?
>
> Our integration application contain camel routes extended using
> RouteBuilder
> API and I see we can use Osgi containers like Fuse / Servicemix or web
> containers like Tomcat, EAP or use Spring Boots.
>
> What would you all suggest? Any of the above options has any
> characteristics
> which qualifies it as best among the lot or perhaps gives an edge of the
> others?
>
> Cheers
> Reji
>
>
>
> -----
> Reji Mathews
> Sr. Developer - Middleware Integration / SOA ( Open Source - Apache Camel
> & Jboss Fuse ESB | Mule ESB )
> LinkedIn - http://in.linkedin.com/pub/reji-mathews/31/9a2/40a
> Twitter - reji_mathews
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-Deployment-Best-Practice-tp5772655.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
Re: Camel Deployment - Best Practice
Posted by Claus Ibsen <cl...@gmail.com>.
If you are not already familiar with OSGi then I would consider not
going for OSGi.
spring-boot, camel-boot and microcontainers are often easier to use.
http://camel.apache.org/camel-boot
And the idea of an app server is being challenged with the new docker
/ cloud like platforms.
https://medium.com/fabric8-io/the-decline-of-java-application-servers-when-using-docker-containers-edbe032e1f30
That said, if you do go with OSGi then Apache Karaf based containers
are the best IMHO. But I am biased.
On Wed, Oct 14, 2015 at 8:12 PM, contactreji <co...@gmail.com> wrote:
> Hello guys
>
> We deliver integration solutions using Apache Camel with big volumes of data
> in production. I was just curious to know what would be the best choice as a
> container?
>
> Our integration application contain camel routes extended using RouteBuilder
> API and I see we can use Osgi containers like Fuse / Servicemix or web
> containers like Tomcat, EAP or use Spring Boots.
>
> What would you all suggest? Any of the above options has any characteristics
> which qualifies it as best among the lot or perhaps gives an edge of the
> others?
>
> Cheers
> Reji
>
>
>
> -----
> Reji Mathews
> Sr. Developer - Middleware Integration / SOA ( Open Source - Apache Camel & Jboss Fuse ESB | Mule ESB )
> LinkedIn - http://in.linkedin.com/pub/reji-mathews/31/9a2/40a
> Twitter - reji_mathews
> --
> View this message in context: http://camel.465427.n5.nabble.com/Camel-Deployment-Best-Practice-tp5772655.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2nd edition:
https://www.manning.com/books/camel-in-action-second-edition