Business level functionality for consideration: Ability to replicate transaction information across multiple sites

, ,
1

Imported from previous forum

2

For example, perhaps you have 3 co-location exchange installations, but need to replicate transaction information between the sites : perhaps a high frequency mechanism for drop copy style reporting should be included in scope?

3

In what way would efficient drop copies be different from efficient messages in general?

For example, perhaps you have 3 co-location exchange installations, but need to replicate transaction information between the sites : perhaps a high frequency mechanism for drop copy style reporting should be included in scope?

4

One thing could be the ability to replicate data to multiple sites more efficiently.

So in the example you have 3 sites that need to share data, how can we most efficiently share the data accross all three locations?

In what way would efficient drop copies be different from efficient messages in general?

For example, perhaps you have 3 co-location exchange installations, but need to replicate transaction information between the sites : perhaps a high frequency mechanism for drop copy style reporting should be included in scope?

5

It is a valid concern but I am not sure that it should be addressed at the protocol design level. FIX Drop uses FIX protocol as is; I see no reason why HFT FIX drop copy can’t follow the same model.
Alternatively, we could consider multicast extensions to HFT FIX. Perhaps this can be considered in the scope of transport discussion.

6

I understand. That is more of a transport issue.

One thing could be the ability to replicate data to multiple sites more efficiently.

So in the example you have 3 sites that need to share data, how can we most efficiently share the data accross all three locations?

In what way would efficient drop copies be different from efficient messages in general?

For example, perhaps you have 3 co-location exchange installations, but need to replicate transaction information between the sites : perhaps a high frequency mechanism for drop copy style reporting should be included in scope?

7

I believe this is covered in FIX through Application Sequencing. You can subscribe to ApplID values from the multiple sites. The sender keeps track of the subscribers and sends a single message to multiple sites. The concept includes retransmission requests and more.

For example, perhaps you have 3 co-location exchange installations, but need to replicate transaction information between the sites : perhaps a high frequency mechanism for drop copy style reporting should be included in scope?