public interface FanOutConfig extends Config
Fan-out is defined as the replication of topics from primary servers (maintaining the 'source' or 'master' versions of the topics) to one or more secondary (or 'edge') servers. Updates to replicated topics on a primary server are fanned out to the replica topics on the secondary servers.
This configuration is used to define fan-out requirements for a secondary server. It is possible to define one or more connections to primary servers in order to replicate all or parts of the topic tree of the primary server(s) to the secondary server.
There can only be one connection defined to any one primary server. The topics to replicate are defined in terms of one or more links representing selections of the topic tree to replicate.
Routing
topics are replicated to secondary servers. The secondary server must have a
local routing topic handler to resolve subscriptions to routing topics.
Note that the following deprecated topic types can not be replicated using
fan-out:
Child
List
Service
Topic
Notify
If any of the above types are found to be present in replicated links then a
warning will be logged to the secondary server and the topic will simply not
be replicated and therefore will not be present on the secondary server.
Modifier and Type | Method and Description |
---|---|
FanOutConnectionConfig |
addConnection(String url)
Add a new connection to a primary server.
|
List<FanOutConnectionConfig> |
getConnections()
Get the configured list of primary server connections.
|
FanOutConnectionConfig addConnection(String url) throws ConfigException
url
- the primary server urlConfigException
- if there is already a connection with the same
urlList<FanOutConnectionConfig> getConnections()
Copyright © 2016 Push Technology Ltd. All Rights Reserved.