Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 cschneider@talend.com does not designate 83.246.65.53 as permitted sender)
From: Christian Schneider <cschneider@talend.com>
To: "users@camel.apache.org" <users@camel.apache.org>
Date: Tue, 29 Mar 2011 14:20:59 +0200
Subject: AW: Service architecture
Thread-Topic: Service architecture
Thread-Index: AcvtRri58YNgfLPaQZymT9O6NJZuOQAwtzbg
Message-ID: 
 <BCCA9B57FEE894408005513A58B8CF1D0622D8CCB5@EXMBX01.SFP-Net.skyfillers.local>
References: <A2304C0501639840B9D248F682E60C65304DA5@aowmail1.dcv.net>
In-Reply-To: <A2304C0501639840B9D248F682E60C65304DA5@aowmail1.dcv.net>
Accept-Language: de-DE, en-US
Content-Language: de-DE
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi Gonzalo,

I am a big fan of camel so don=B4t understand me wrong.=20

If you are using JEE all over the place then you should at least think abou=
t migrating to JEE6 I am regularly reading the blog prosts of Adam Bien and=
 from what he writes the modern JEE implementation could be a great platfor=
m. I never really did JEE as it really sucked below EJB 3 but I think it ha=
s become quite good. Using JEE would allow you to use the knowledge your de=
velopers have with it.

Having said that camel will also be a great platform to build your applicat=
ions on. Especially when you do the step to OSGi nd Karaf like Achim sugges=
ted. OSGi has a steep learning curve though so be prepared for some problem=
s at the start.

For async Services  I really like camel=B4s pojo messaging with jms. Where =
you use a plain java interface for the handler. The serialization can be Ja=
va serialization or JAXB. This is very simple to setup.
For synchronous calls you have to decide between SOAP and REST or even Spri=
ng HttpInvoker.=20
If you want to create client code then SOAP will be better. If you go java =
first then REST or HTTPInvoker are simpler. For multi language SOAP again m=
ay be easier but REST will also be possible with e.b. JAXB seralzation.

So what I propose is that  you invite specialists for the apache stack (Cam=
el, CXF, Karaf) and specialists for JEE and let them create a POC scenario.=
 Then you can decide which looks better.
>From my point of view I think JEE will be simpler to get running but less i=
nnovative and less open. The apache stack above will be more complex to set=
up but provide more flexibility. So it will be a tradeoff like always in ar=
chitecture.

Christian
http://www.liquid-reality.de

-----Urspr=FCngliche Nachricht-----
Von: gonzalo diethelm [mailto:gdiethelm@dcv.cl]=20
Gesendet: Montag, 28. M=E4rz 2011 14:51
An: users@camel.apache.org
Betreff: Service architecture

This is my first post to this list, and I declare myself a Camel newbie.  L=
et me start by first saying that Camel is great; a big thanks to the whole =
team for such a wonderful piece of engineering.

I have been searching for some time now for a new way (to me) to build a se=
rvice architecture, to be used _within_ the company; that is, this is not i=
ntended for web facing services, at least not directly, but more for the "p=
ure" business logic layer.  My goals for this service architecture are:

1. Light-weight.
2. Easy to use for callers of services.
3. Support for synchronous (RPC) and asynchronous (MOM) invocation styles.
4. Ability to invoke services from different languages (desired).


Thanks in advance for any wisdom shared, and best regards.

--=20
Gonzalo Diethelm=20