Impact of network latency
In the context of file/registry replication, each transmission is followed by acknowledgment from the peer application node. This means that the impact of replication is approximately a product of the number of files to be transferred times the packet response time. For example, to replicate 100 files over a 100ms network, a total of 20 seconds of packet latency overhead is introduced per pair of replicated nodes.
In the context of database replication, each batch of stored procedure calls is impacted by the latency twice per TCP receive window size. The TCP receive window size is an operating system parameter, typically between 8KB and 64KB. In general, throughput drops as latency increases, but this is not normally a problem so long as latency is well under 500ms per packet and overall transaction volumes are "normal".
Best practice
Bravura Security recommends placing all Bravura Security Fabric servers which made up a database node at locations with no more than 150ms latency between them.
In practice, high network latency (where application nodes are on opposite sides of a continent or separated by an ocean) has the following impact:
The time required to complete file/registry replication during nightly auto-discovery will grow by several minutes per pair of replicated application nodes.
The time required to complete database replication for large volumes of data – during nightly auto discovery and under heavy load conditions – can grow from seconds to minutes.