You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by nitingupta183 <ni...@gmail.com> on 2008/09/26 15:08:33 UTC
Camel + Seda
Hi all,
In my application, I am thinking of using SEDA Camel component to achieve
async communication between two processes. Since I am new to SEDA, I would
like to have ur opinion on following:
- Is it right to use SEDA? I mean does it have any impact on the performance
(in bad way) of the application?
- Is it the standard practice between Camel developers to use it for the
asynchronous communication between processes which are time intensive?
Any pointers which can lead to SEDA based implementations and the concerns,
shall be highly appreciated.
Regards,
nitin
--
View this message in context: http://www.nabble.com/Camel-%2B-Seda-tp19688151s22882p19688151.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel + Seda
Posted by cmoulliard <cm...@gmail.com>.
Hi Nitin,
Please have a look to the following link for more information about SEDA :
You can check out the SEDA component wiki documentation:
http://activemq.apache.org/camel/seda.html
And comparison between the different endpoints (direct, seda, vm, ...)
http://activemq.apache.org/camel/how-do-the-direct-event-seda-and-vm-endpoints-compare.html
And the source code:
https://svn.apache.org/repos/asf/activemq/camel/trunk/camel-core/src/main/java/org/apache/camel/component/seda/
Kind regards,
Charles Moulliard
nitingupta183 wrote:
>
> Hi all,
>
> In my application, I am thinking of using SEDA Camel component to achieve
> async communication between two processes. Since I am new to SEDA, I would
> like to have ur opinion on following:
>
> - Is it right to use SEDA? I mean does it have any impact on the
> performance (in bad way) of the application?
> - Is it the standard practice between Camel developers to use it for the
> asynchronous communication between processes which are time intensive?
>
> Any pointers which can lead to SEDA based implementations and the
> concerns, shall be highly appreciated.
>
> Regards,
> nitin
>
-----
Enterprise Architect
Xpectis
12, route d'Esch
L-1470 Luxembourg
Phone +352 25 10 70 470
Mobile +352 621 45 36 22
e-mail : cmoulliard@xpectis.com
web site : www.xpectis.com www.xpectis.com
My Blog : http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/
--
View this message in context: http://www.nabble.com/Camel-%2B-Seda-tp19688151s22882p19689066.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel + Seda
Posted by nitingupta183 <ni...@gmail.com>.
Hi James,
Bu process I meant, the application process i.e. inside the same JVM.
Thanks for the clarification.
Regards,
Nitin
James.Strachan wrote:
>
> 2008/9/27 nitingupta183 <ni...@gmail.com>:
>> Hi Claus,
>>
>> I intend to use SEDA endpoint to asynchronously call a process from
>> another
>> process as I think that the called process can be time intensive. So
>> unless
>> it is not made to act in the async mode, then app users' wait time is
>> gonna
>> go rise.
>
> Sounds good.
>
> BTW when you say 'process' do you mean operating system process or are
> we talking about in the same JVM here. If its separate processes then
> the seda endpoint won't work (it only works for producers and
> consumers within the same JVM) - instead try looking at JMS or file
> endpoints...
> http://activemq.apache.org/camel/jms.html
>
>
>> Is it a valid use case for using SEDA? As you can see, my purpose is just
>> to
>> make the called process work in its own thread so that the calling thread
>> can return in quick time.
>
> Definitely!
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://open.iona.com
>
>
--
View this message in context: http://www.nabble.com/Camel-%2B-Seda-tp19688151s22882p19754303.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel + Seda
Posted by James Strachan <ja...@gmail.com>.
2008/9/27 nitingupta183 <ni...@gmail.com>:
> Hi Claus,
>
> I intend to use SEDA endpoint to asynchronously call a process from another
> process as I think that the called process can be time intensive. So unless
> it is not made to act in the async mode, then app users' wait time is gonna
> go rise.
Sounds good.
BTW when you say 'process' do you mean operating system process or are
we talking about in the same JVM here. If its separate processes then
the seda endpoint won't work (it only works for producers and
consumers within the same JVM) - instead try looking at JMS or file
endpoints...
http://activemq.apache.org/camel/jms.html
> Is it a valid use case for using SEDA? As you can see, my purpose is just to
> make the called process work in its own thread so that the calling thread
> can return in quick time.
Definitely!
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://open.iona.com
RE: Camel + Seda
Posted by nitingupta183 <ni...@gmail.com>.
Hi Claus,
I intend to use SEDA endpoint to asynchronously call a process from another
process as I think that the called process can be time intensive. So unless
it is not made to act in the async mode, then app users' wait time is gonna
go rise.
Is it a valid use case for using SEDA? As you can see, my purpose is just to
make the called process work in its own thread so that the calling thread
can return in quick time.
Regards,
Nitin
Claus Ibsen wrote:
>
> Hi
>
> I think a few months ago there was a discussion about advanced SEDA from
> an end-user with James Strachan. Try searching the forums.
>
> - Yes it's very good for separation of routes in async parts.
>
> See this wiki page as well (related as its about async)
> http://activemq.apache.org/camel/asynchronous-processing.html
>
>
>
> Med venlig hilsen
>
> Claus Ibsen
> ......................................
> Silverbullet
> Skovsgårdsvænget 21
> 8362 Hørning
> Tlf. +45 2962 7576
> Web: www.silverbullet.dk
>
> -----Original Message-----
> From: nitingupta183 [mailto:nitingupta183@gmail.com]
> Sent: 26. september 2008 15:09
> To: camel-user@activemq.apache.org
> Subject: Camel + Seda
>
>
> Hi all,
>
> In my application, I am thinking of using SEDA Camel component to achieve
> async communication between two processes. Since I am new to SEDA, I would
> like to have ur opinion on following:
>
> - Is it right to use SEDA? I mean does it have any impact on the
> performance
> (in bad way) of the application?
> - Is it the standard practice between Camel developers to use it for the
> asynchronous communication between processes which are time intensive?
>
> Any pointers which can lead to SEDA based implementations and the
> concerns,
> shall be highly appreciated.
>
> Regards,
> nitin
> --
> View this message in context:
> http://www.nabble.com/Camel-%2B-Seda-tp19688151s22882p19688151.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
>
--
View this message in context: http://www.nabble.com/Camel-%2B-Seda-tp19688151s22882p19701999.html
Sent from the Camel - Users mailing list archive at Nabble.com.
RE: Camel + Seda
Posted by Claus Ibsen <ci...@silverbullet.dk>.
Hi
I think a few months ago there was a discussion about advanced SEDA from an end-user with James Strachan. Try searching the forums.
- Yes it's very good for separation of routes in async parts.
See this wiki page as well (related as its about async)
http://activemq.apache.org/camel/asynchronous-processing.html
Med venlig hilsen
Claus Ibsen
......................................
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
Web: www.silverbullet.dk
-----Original Message-----
From: nitingupta183 [mailto:nitingupta183@gmail.com]
Sent: 26. september 2008 15:09
To: camel-user@activemq.apache.org
Subject: Camel + Seda
Hi all,
In my application, I am thinking of using SEDA Camel component to achieve
async communication between two processes. Since I am new to SEDA, I would
like to have ur opinion on following:
- Is it right to use SEDA? I mean does it have any impact on the performance
(in bad way) of the application?
- Is it the standard practice between Camel developers to use it for the
asynchronous communication between processes which are time intensive?
Any pointers which can lead to SEDA based implementations and the concerns,
shall be highly appreciated.
Regards,
nitin
--
View this message in context: http://www.nabble.com/Camel-%2B-Seda-tp19688151s22882p19688151.html
Sent from the Camel - Users mailing list archive at Nabble.com.