The standard DataSync method that we provide is one to one. You define a shared queue on your source that will generate one message to share to. One target application (the DataSync Agent, meshlet, Perspectium Core ServiceNow app, etc.) will subscribe to the same queue to read the message. If you are sharing from one source and intend to send the same data to several different targets (data warehouses, dev instances, test instances) you may have noticed that you will have to create as many duplicate share configurations (bulk shares and dynamic shares) as you have targets.
For simple sharing to two or three destinations this is very manageable, but if you plan on sharing out towards several destinations this can be cumbersome. To solve this, we have the capability to perform one to many syncing which we refer to as a fanout queue. You send your data once to a single shared queue and then MBS will fanout the message to multiple other queues for different target applications to each read a copy of the same message from a different queue.
- Fanout queues can only be configured by Perspectium. Contact support@perspectium.com with your desired fanout queue configuration so we can set this up.
NOTE: Since we have to configure the fanout queue and the queues it sends the messages to, there is a small downtime window when you will not be able to share to the fanout queue or subscribe to the queues it sends the messages to. You will need to coordinate with Perspectium for fanout queue configuration to account for this downtime.- Fanout queues do not contain a copy of the original message. The fanout queue is intended to forward copies of the message to other queues and is not a queue that is consumed from directly.
- As a result of not containing a copy of the message, fanout queues do not work with Get Queue Status.
For example, you can set up a shared queue that will fanout to multiple queues as follows:
Shared Queue (in Perspectium Core ServiceNow Application) | Subscribed Queues (in Target Applications) |
|---|---|
| psp.out.replicator.company.fanout | psp.out.replicator.company.data1 |
| psp.out.replicator.company.data2 | |
| psp.out.replicator.company.data3 | |
| psp.out.servicenow.company.dev | |
| psp.out.servicenow.company.test |
In this case you will share out from your ServiceNow instance (using bulk shares and dynamic shares) to psp.out.replicator.company.fanout which will then send a copy of each message to psp.out.replicator.company.data1, psp.out.replicator.company.data2, psp.out.replicator.company.dev and psp.out.replicator.company.test. You then configure your DataSync Agent, meshlets, ServiceNow instances, etc. to subscribe to the queues psp.out.replicator.company.data1, psp.out.replicator.company.data2, psp.out.replicator.company.dev and psp.out.replicator.company.test to read into the target systems.
To setup a fanout queue, contact us at support@perspectium.com in order for us to know your requirements and how we can best create your desired structure.
