Selecting decision services for execution

Executing the most recently deployed, latest semantic, or last sorted version

When a new version of a decision service is deployed, it is automatically selected for execution. Your client application does not need to be changed or aware of the decision ID of the decision service to be executed.

The resolution of the selected decision is cached, and the cache update it subject to a configurable delay. You can configure this delay in the update_interval parameter. As a consequence, if a decision service is deployed just after the execution request of the previously deployed decision service, the previously deployed decision service might be executed instead of the last deployed decision service.

For more information, see ads_configuration.decision_runtime_service.decision_selection parameters in Decision runtime parameters.

Executing a specific version

Your client application does not need to be aware of the decision ID of the decision service to be executed. However, it needs to be aware of the deployed decision service versions, and specify which version to get selected.

This strategy can be used when a new deployment of a decision service is not necessarily used immediately. For example, you can use it when a new version applies discounts for certain items, and these discounts can be used on a specified date.