You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by "Sam (Stephen Samuel)" <sa...@gmail.com> on 2012/07/18 16:28:04 UTC
Camel Routes across JVMs
Hi,
What's the best practice for having routes communicate across VMs?
Specifically speaking I want an application to send messages to
another on a separate server and the 2nd server to process those
messages in its own camel route.
Re: Camel Routes across JVMs
Posted by Bilgin Ibryam <bi...@gmail.com>.
You can also use pub/sub feature of redis http://redis.io/topics/pubsub
I am working on a camel-redis component and we are also planning to use
this feature of redis to send notifications between apps. The connector is
still WIP but will be ready soon hopefully.
https://github.com/bibryam/camel-redis
Bilgin
On 18 July 2012 16:18, Sam (Stephen Samuel) <sa...@gmail.com> wrote:
> Ah I missed that. Thanks.
>
> On Wed, Jul 18, 2012 at 3:50 PM, thomas barker
> <th...@gmail.com> wrote:
> > I guess it does: http://camel.apache.org/hazelcast-component.html
> >
> > To be honest there are many options to get this to work, so I would use
> > whatever you know best and are most comfortable with. If you don't want
> to
> > rock the boat, most people here probably have more experience with
> camel's
> > jms support than any other option mentioned.
> >
> >
> > On Wed, Jul 18, 2012 at 10:45 AM, Sam (Stephen Samuel)
> > <sa...@gmail.com> wrote:
> >>
> >> I'll stick with JMS then, didn't know if Camel had some kind of
> >> Hazelcast type thing.
> >>
> >> On Wed, Jul 18, 2012 at 3:39 PM, thomas barker
> >> <th...@gmail.com> wrote:
> >> > If you use JMS use activemq if you can... the http / servlet / jetty
> >> > components are lightweight options as well.
> >> >
> >> > On Wed, Jul 18, 2012 at 10:36 AM, Charles <cw...@yahoo.com> wrote:
> >> >
> >> >> 1.) Use JMS
> >> >> 2.) Use CXF (web services)
> >> >>
> >> >> I've done #1, it's probably easier.
> >> >>
> >> >>
> >> >> ----- Original Message -----
> >> >> From: Sam (Stephen Samuel) <sa...@gmail.com>
> >> >> To: users@camel.apache.org
> >> >> Cc:
> >> >> Sent: Wednesday, July 18, 2012 10:28 AM
> >> >> Subject: Camel Routes across JVMs
> >> >>
> >> >> Hi,
> >> >>
> >> >> What's the best practice for having routes communicate across VMs?
> >> >> Specifically speaking I want an application to send messages to
> >> >> another on a separate server and the 2nd server to process those
> >> >> messages in its own camel route.
> >> >>
> >> >>
> >>
> >>
> >>
> >> --
> >> -Sam
> >
> >
>
>
>
> --
> -Sam
>
Re: Camel Routes across JVMs
Posted by "Sam (Stephen Samuel)" <sa...@gmail.com>.
Ah I missed that. Thanks.
On Wed, Jul 18, 2012 at 3:50 PM, thomas barker
<th...@gmail.com> wrote:
> I guess it does: http://camel.apache.org/hazelcast-component.html
>
> To be honest there are many options to get this to work, so I would use
> whatever you know best and are most comfortable with. If you don't want to
> rock the boat, most people here probably have more experience with camel's
> jms support than any other option mentioned.
>
>
> On Wed, Jul 18, 2012 at 10:45 AM, Sam (Stephen Samuel)
> <sa...@gmail.com> wrote:
>>
>> I'll stick with JMS then, didn't know if Camel had some kind of
>> Hazelcast type thing.
>>
>> On Wed, Jul 18, 2012 at 3:39 PM, thomas barker
>> <th...@gmail.com> wrote:
>> > If you use JMS use activemq if you can... the http / servlet / jetty
>> > components are lightweight options as well.
>> >
>> > On Wed, Jul 18, 2012 at 10:36 AM, Charles <cw...@yahoo.com> wrote:
>> >
>> >> 1.) Use JMS
>> >> 2.) Use CXF (web services)
>> >>
>> >> I've done #1, it's probably easier.
>> >>
>> >>
>> >> ----- Original Message -----
>> >> From: Sam (Stephen Samuel) <sa...@gmail.com>
>> >> To: users@camel.apache.org
>> >> Cc:
>> >> Sent: Wednesday, July 18, 2012 10:28 AM
>> >> Subject: Camel Routes across JVMs
>> >>
>> >> Hi,
>> >>
>> >> What's the best practice for having routes communicate across VMs?
>> >> Specifically speaking I want an application to send messages to
>> >> another on a separate server and the 2nd server to process those
>> >> messages in its own camel route.
>> >>
>> >>
>>
>>
>>
>> --
>> -Sam
>
>
--
-Sam
Re: Camel Routes across JVMs
Posted by thomas barker <th...@gmail.com>.
I guess it does: http://camel.apache.org/hazelcast-component.html
To be honest there are many options to get this to work, so I would use
whatever you know best and are most comfortable with. If you don't want to
rock the boat, most people here probably have more experience with camel's
jms support than any other option mentioned.
On Wed, Jul 18, 2012 at 10:45 AM, Sam (Stephen Samuel) <samspade79@gmail.com
> wrote:
> I'll stick with JMS then, didn't know if Camel had some kind of
> Hazelcast type thing.
>
> On Wed, Jul 18, 2012 at 3:39 PM, thomas barker
> <th...@gmail.com> wrote:
> > If you use JMS use activemq if you can... the http / servlet / jetty
> > components are lightweight options as well.
> >
> > On Wed, Jul 18, 2012 at 10:36 AM, Charles <cw...@yahoo.com> wrote:
> >
> >> 1.) Use JMS
> >> 2.) Use CXF (web services)
> >>
> >> I've done #1, it's probably easier.
> >>
> >>
> >> ----- Original Message -----
> >> From: Sam (Stephen Samuel) <sa...@gmail.com>
> >> To: users@camel.apache.org
> >> Cc:
> >> Sent: Wednesday, July 18, 2012 10:28 AM
> >> Subject: Camel Routes across JVMs
> >>
> >> Hi,
> >>
> >> What's the best practice for having routes communicate across VMs?
> >> Specifically speaking I want an application to send messages to
> >> another on a separate server and the 2nd server to process those
> >> messages in its own camel route.
> >>
> >>
>
>
>
> --
> -Sam
>
Re: Camel Routes across JVMs
Posted by "Sam (Stephen Samuel)" <sa...@gmail.com>.
I'll stick with JMS then, didn't know if Camel had some kind of
Hazelcast type thing.
On Wed, Jul 18, 2012 at 3:39 PM, thomas barker
<th...@gmail.com> wrote:
> If you use JMS use activemq if you can... the http / servlet / jetty
> components are lightweight options as well.
>
> On Wed, Jul 18, 2012 at 10:36 AM, Charles <cw...@yahoo.com> wrote:
>
>> 1.) Use JMS
>> 2.) Use CXF (web services)
>>
>> I've done #1, it's probably easier.
>>
>>
>> ----- Original Message -----
>> From: Sam (Stephen Samuel) <sa...@gmail.com>
>> To: users@camel.apache.org
>> Cc:
>> Sent: Wednesday, July 18, 2012 10:28 AM
>> Subject: Camel Routes across JVMs
>>
>> Hi,
>>
>> What's the best practice for having routes communicate across VMs?
>> Specifically speaking I want an application to send messages to
>> another on a separate server and the 2nd server to process those
>> messages in its own camel route.
>>
>>
--
-Sam
Re: Camel Routes across JVMs
Posted by thomas barker <th...@gmail.com>.
If you use JMS use activemq if you can... the http / servlet / jetty
components are lightweight options as well.
On Wed, Jul 18, 2012 at 10:36 AM, Charles <cw...@yahoo.com> wrote:
> 1.) Use JMS
> 2.) Use CXF (web services)
>
> I've done #1, it's probably easier.
>
>
> ----- Original Message -----
> From: Sam (Stephen Samuel) <sa...@gmail.com>
> To: users@camel.apache.org
> Cc:
> Sent: Wednesday, July 18, 2012 10:28 AM
> Subject: Camel Routes across JVMs
>
> Hi,
>
> What's the best practice for having routes communicate across VMs?
> Specifically speaking I want an application to send messages to
> another on a separate server and the 2nd server to process those
> messages in its own camel route.
>
>
Re: Camel Routes across JVMs
Posted by Charles <cw...@yahoo.com>.
1.) Use JMS
2.) Use CXF (web services)
I've done #1, it's probably easier.
----- Original Message -----
From: Sam (Stephen Samuel) <sa...@gmail.com>
To: users@camel.apache.org
Cc:
Sent: Wednesday, July 18, 2012 10:28 AM
Subject: Camel Routes across JVMs
Hi,
What's the best practice for having routes communicate across VMs?
Specifically speaking I want an application to send messages to
another on a separate server and the 2nd server to process those
messages in its own camel route.