You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/03/07 19:40:00 UTC

[jira] [Commented] (ARTEMIS-2265) Support Federated Queues and Addresses

    [ https://issues.apache.org/jira/browse/ARTEMIS-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787137#comment-16787137 ] 

ASF subversion and git services commented on ARTEMIS-2265:
----------------------------------------------------------

Commit 4a5af776d87f3313fe7bd67309dc9d2bc8cc2e45 in activemq-artemis's branch refs/heads/master from Michael André Pearce
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=4a5af77 ]

ARTEMIS-2265 Support Federated Queues and Addresses 

Implement Federated Queue (builds on recent consumer priority)
Implement Federated Address (builds on recent queue level auto-delete)
Add Functional Tests
Add Failure Tests (remote and local shutdowns)
Add Documentation


> Support Federated Queues and Addresses
> --------------------------------------
>
>                 Key: ARTEMIS-2265
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2265
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Michael Andre Pearce
>            Priority: Major
>          Time Spent: 4h 20m
>  Remaining Estimate: 0h
>
> Currently Artemis supports linking of brokers via clustering that are within the same DC or AZ. 
> It is not sensible to form clusters though over high latency or unreliable networks, e.g. WAN, cross-region in cloud, hybrid on-off premise etc.
> Bridges exist, but these are static.
> In ActiveMQ5 there was a concept of Network of Brokers, and like wise in RabbitMQ there is a concept of Federation, both of these try an deal with this issue.
>  
> This is to implement similar functionality in Artemis.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)