Orchestrator Read-only Replica

Orchestrator maintains a read-only replica of its read-write operational database, with the main purpose of improving performance. Some read-only workloads are directed towards the read-only replica, so as to optimize write-replica consumption. This allows data to be read and loaded faster, which, in turn, ensures the performance of your system.

As a result of this implementation, a slight delay between the write and read actions might occur. This is to be expected, and has no impact on data becoming available.

An example of this scenario is retrieving a queue item as soon as it was added: when performed from the interface, the new queue items might not be displayed instantly, as there is a slight asynchronicity between the operational database (where the item is written) and the replica (which is called for reading the item). You can, however, avoid this by using the Get transaction item activity instead of Get queue items, since the former includes the queue item in its response.

Use cases

If your database supports a read-only replica (ApplicationIntent=ReadOnly), Orchestrator will use it to retrieve the following items:

• queue items
• monitoring data
  Note: The value of the Database.HonorReadIntentRequests parameter has no impact on monitoring.
• jobs data

Otherwise, Orchestrator will use the read-write database.