Throttle Plugin
- Ben Clark
Overview
Rules run in Alterian Journey Orchestration run very, very quickly. This step allows rules that can be throttled allowing smoother integrations with third parties that just can’t react fast enough.
Provides the ability to have joint throttle limits across multiple rules using the resource name to link the throttles together.
Example:
Our users want to call a third-party solution but the third-party solution is not able to cope with the number of requests our Rules can create per second. The throttle plugin allows our users to throttle the number of requests to a level the third-party system can cope with.
Plugin Configuration
The following settings can be configured:
Setting | Description |
|---|---|
Step Name | Allows the Step to be given a unique descriptive name. |
Server Name | Name of the Journey Orchestration system that will store the up to date throttle information |
Key space | Name of the key space in Journey Orchestration that will store the up to date throttle information |
Resource Name | This is where the up to date throttle logic is stored. This value is created as a parameter so it can easily be changed through the UI but this value can be hard coded in the step if required. If the Server, Keyspace and Resource Name are the same the same throttle limits can be applied across multiple rules. This is useful if you have multiple rules in parallel calling out the same solution. |
Row Limit | Specify the number of rows that will be output per second. The default is 1 |