I'm glad to have a chance of asking you these questions, as I'm right after quite absorbing lecture about SOA and integration/adoption of some really heavy, big, demanding and very distributed environment. I believe it's a plan for next years. There was listed some options during the lecture for tools to support the apporach. There was a Camel on the list as well. I'm just wondering, which of SOA principles/layers Camel supports for sure, and which it doesn't? If it doesn't any of them, what kind of frameworks/approaches would you recommend to fill the gap and tie it with Camel to have effective SOA - it is OK if you write here: it is in the book? Is domain controlling and business orchestrating coverd by Camel? It probably is, if so, how?
And last one: What is interesting in your book for guys (let's call them: newbies) working on real SOA?
1. My company recently started using Open Message Queue (the Sun implementation of JMS) in its applications. Would we have to switch to ActiveMQ to use the Camel framework?
2. I was looking into Camel a few weeks ago, and downloaded the install file. It seemed (from the size of the download) to be a huge install. My first impression was that it would be heavyweight to run, sucking up lots of CPU cycles. Is this the case?
3. How steep is the learning curve for Camel?
Could you comment briefly on what this is and does, beyond the obvious?
Is it intended to be essentially Camel-centric, or a more generic enhancement / replacement for such tools as junit?
Is it intended as a primary vehicle for verifying enhancements / user-created plugins to Camel?
Does it include routines suitable for measuring (or optimizing :P) Camel code performance and/or scalability?