Re: Qpid broker federation use case info?

[mark yoffe <ma...@gmail.com>]

Hi

can anyone explain the benefits of federation

and the proposed use scenario's

furthermore it is supproted in M3
and in Trunk?

On Thu, Oct 30, 2008 at 10:06 PM, Ted Ross <tr...@redhat.com> wrote:

>  gregory james marsh wrote:
>
>> Hello,
>>
>> I'm experimenting with Qpid broker federation functionality.  I've noticed
>> that there are a number of concepts and scenarios listed on the following
>> page:
>>
>> http://cwiki.apache.org/qpid/using-broker-federation.html
>>
>> However, there are no links with details for each item on the list.  Does
>> anybody have any references/links to further information about these
>> scenarios.
>>
>> Thanks,
>>
>> Greg Marsh
>>
>>
>>
>>
>>
> Hi Greg,
>
> I'm planning to start fleshing out that Wiki page starting next week.
>  There are some new federation features that make it much easier to
> configure that need to be written up.  These features are in place on the
> Subversion trunk and will be included in the soon-to-be-released M4 release.
>  They are implemented only on the C++ broker at present.
>
> In the mean time, I'd be happy to help get you started and answer any
> questions you'd like to ask on the mailing list.
>
> Do you have a particular use-case in mind?
>
> I'll send out some setup scripts that illustrate various federation
> topologies.
>
> Regards,
>
> -Ted
>
>

Re: Qpid broker federation use case info?

[Carl Trieloff <cc...@redhat.com>]

mark yoffe wrote:
> Hi
>
> can anyone explain the benefits of federation
>
> and the proposed use scenario's
>
> furthermore it is supproted in M3
> and in Trunk?


difference between federation and cluster is probably the first thing to 
comment on.

Clustering give HA, Federation allows you to build networks of brokers.

These networks can be used in many ways, some examples are

multi data center ( have broker in one data center  A and another one in 
data center B). All the
clients can connect to the local broker, and can consume from client 
publishing in the remote
data center.

Load distribution, tree type patterns a can be configured for such cases..

abstraction/scaling - federation can be used to domain or scale a 
deployment.

Basically, you can build any tree, mesh or hub-spoke model with federation.

I think of it as follows: When you use qpid-route, the links are like 
wiring machines
together with network cable. How are the connections patched.

Then, in M3 you can create static routes, like static IP tables. In M4 
(trunk) you can setup
routes to be fully dynamic (lot easier to admin)

easiest is to just start a few brokers on your local machine with 
different ports and wire a few
cases together.

Carl.

Re: Qpid broker federation use case info?

[Carl Trieloff <cc...@redhat.com>]

mark yoffe wrote:
> Hi
>
> can anyone explain the benefits of federation
>
> and the proposed use scenario's
>
> furthermore it is supproted in M3
> and in Trunk?


difference between federation and cluster is probably the first thing to 
comment on.

Clustering give HA, Federation allows you to build networks of brokers.

These networks can be used in many ways, some examples are

multi data center ( have broker in one data center  A and another one in 
data center B). All the
clients can connect to the local broker, and can consume from client 
publishing in the remote
data center.

Load distribution, tree type patterns a can be configured for such cases..

abstraction/scaling - federation can be used to domain or scale a 
deployment.

Basically, you can build any tree, mesh or hub-spoke model with federation.

I think of it as follows: When you use qpid-route, the links are like 
wiring machines
together with network cable. How are the connections patched.

Then, in M3 you can create static routes, like static IP tables. In M4 
(trunk) you can setup
routes to be fully dynamic (lot easier to admin)

easiest is to just start a few brokers on your local machine with 
different ports and wire a few
cases together.

Carl.