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 <[email protected]> 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
