Hi Pavel,
I guess for me, the thing is that ServiceMix *is* an umbrella project
for Karaf, ActiveMQ, Camel and CXF. If you wish, you can start with a
vanilla Karaf container, and then configure all your stuff in; the nice
thing about ServiceMix is that we handle all that packaging. The
ServiceMix project also provides lots of OSGi-ified bundles that you may
need in your work; and, importantly, it provides the ServiceMix NMR
(different from the XML-based JBI NMR!) as some additional smarts for
allowing bundles to communicate with each other beyond OSGi service
references.
James Strachan made a nice comment on this mailing list that ServiceMix
has done an excellent job of making its components very modular - you
can use them by themselves, or you can use them all together.
Guillaume will have more to say in terms of the queue. I know he's
working on some stuff around Activiti BPMN. There's also ongoing work on
improving the core, improving support for OSGi blueprint in Camel, there
some packaging stuff for easy deployment I'm working on (if I get more
time!), and a whole lot more.
Cheers,
Ade.
On 12/11/2010 11:29, Pavel Tavoda wrote:
Thank you Adrian. Yes it was very helpful.
When I evaluate my requirements again I don't see real value by adding
ServiceMix. I can do everything just by working with all this
interesting products like Karaf, ActiveMQ, Camel and maybe ServiceMix
and CXF only for interoperability with "external" systems.
I see you work at core of this projects. When I read roadmaps on
projects they look little bit outdated. What's next in queue? Do you
work on something interesting?
Pavel
On Thu, Nov 11, 2010 at 7:13 PM, Adrian Trenaman<[email protected]> wrote:
Hi Pawel,
Check out some of my slides on http://slideshare.net/trenaman ... They might be
of help!
Best,
Ade
http://fusesource.com
----- Original Message -----
From: Pavel Tavoda [mailto:[email protected]]
Sent: Thursday, November 11, 2010 12:57 PM
To: [email protected]<[email protected]>
Subject: Big picture
Hello,
I read nearly all important materials about ServiceMix (4) but I can't
find big picture for big deployment of ServiceMix. Let's say I'm at
begging of writing applications (about 4-5 applications) which I would
like to integrate very flexible way. Application alone will be single
purpose but with different type of integration you can achieve
interesting results. I don't know how to apply ServiceMix in it.
Services have to be fault tolerant (same service running on multiple
physical servers) and scalable. I would like to also have one central
brain with one configuration which will decide what to do and how to
integrate (of course this central brain have to be also fault
tolerant).
My idea was to use strong messaging (ActiveMQ) with Event Drive
Programming for services. And than having "orchestration" layer which
will run BPEL, Rules, ... and only transform messages from one service
for other services. Important questions for me:
- Because I have no heterogeneous environment and I'm going to write
application from scratch do I need ServiceMix?
- Should I run ServiceMix in every node of my network and deploy
services inside?
- Should I run application in OSGi runtimes (or any other runtime) and
have only one ServiceMix instance for orchestration (my central
brain)?
- Should I run ServiceMix only on border of my system just to
integrate with rest of universe?
- What is best architecture for this purpose?
I would like to have flexible runtime environemt, flexibility in
deployment, and simple reconfiguration of orchestration layer.
I feel lost, thank you for your responses.
Pavel
--
Adrian Trenaman, Sr. Principal Solution Architect
FuseSource
Phone: +353-86-6051026
Email: [email protected]
Web: http://trenaman.blogspot.com, http://fusesource.com
Twitter: adrian_trenaman
