Data Replication Queue

Whenever an event, such as a password change, login, or request submission, occurs on a single Bravura Security Fabric server, information about the event is stored on the local database instance dedicated to that Bravura Security Fabric server. It is replicated to all other Bravura Security Fabric servers, each with their own physically distinct database instance.

This replication happens in real time as long as the Bravura Security Fabric database services are connected to the respective Bravura Security Fabric servers.

If a given Bravura Security Fabric server (henceforth called originator) cannot contact the database service on another Bravura Security Fabric server (henceforth called replica), the update is queued on the originator’s file system in queue files.

If real-time replication stops and the queue starts to fill, the originator Bravura Security Fabric server will stop functioning when the queue is full. This is because the alternative would be to write updates to the originator’s database without replicating them to other servers, creating a single point of failure in the system.