Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <49E6C2CF.4050101@martin-krasser.de>
Date: Thu, 16 Apr 2009 07:31:59 +0200
From: Martin Krasser <dev@martin-krasser.de>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: users@camel.apache.org
Subject: Re: Camel in Production
References: <23065752.post@talk.nabble.com>
In-Reply-To: <23065752.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Samarth,

we're using Camel in the Open eHealth Integration Platform (IPF) [1]. 
IPF is deployed in clinical environments in Europe and US. The focus is 
on HL7 message processing and IHE profiles. IPF has also been tested 
successfully at the Connect-a-thon 2009[2] for the IHE profiles PIX and 
PDQ. After working now 1.5 years with Camel we're still convinced that 
it is the right basis for IPF not only in terms of quality and feature 
richness but also in terms for developer productivity.

[1] http://gforge.openehealth.org/gf/project/ipf/
[2] http://www.ihe.net/north_america/connectathon2009.cfm

Cheers,
Martin

samarthbhargava schrieb:
> Hi,
> I am evaluating Spring Integration, Camel & JBPM to implement workflows. 
> I was looking for some case studies/projects that are using Camel and have
> deployed it in production. I would also like to know whether there are any
> performance benchmarks for Camel that can demonstrate the scalability of the
> framework.
>
> If anyone has done a similar exercise, it would be great if you can share
> the results.
>
> Regards,
> Samarth 
>