Improved License Server and REST Server Behaviour

With the introduction of these new server improvements, it is now possible to have as many REST servers running as you'd like. This number is no longer capped by the number of CO’s (Concurrent Operations) your license allows. The CO capacity will now only limit the total amount of concurrent operations running across all REST servers linked to that license.

The Old

The old implementation would require each REST server, upon startup, to be allotted an amount of the total CO capacity your license allows for. This meant that at most the total number of REST servers that could be started would equal that of the total CO capacity, even if no comparisons were running on any of them, disadvantaging scalability and efficiency. Any attempt to further startup servers would result in a “Concurrency Limit Reached” exception. As shown in the diagram below.

The New

The new implementation now allows for any number of REST servers to be spun up without detracting from CO capacity. The capacity is now only limiting the total number of CO’s running across all servers no matter the number of servers. This means hyper scalability and efficient use of servers can be achieved to meet increased CO’s traffic. When an attempt to submit an operation to any server whilst the CO limit is maxed, the operation is then queued within the license server and will begin when a CO becomes available i.e by completion or cancelling of a previously running operation making a capacity slot free. Queuing is done on a first come first served basis and does not have a limit to the length of the queue.

The diagram below shows the new behaviour.

The Old

The New