Abstract: A mechanism is provided in a data processing system for automatically throttling the rate of service provided by a Web application programming interface (API) for a software service. A flow controller executing on the data processing system assigns a queue to each consumer of the software service. Responsive to receiving a current request for the software service from a given consumer of the software service, a flow controller executing on the data processing system adds the current request to a given queue assigned to the given consumer. The flow controller sends a next request from the given queue to the Web API based on a licensed rate of service of the given consumer.

Abstract: A mechanism is provided in a data processing system for automatically throttling the rate of service provided by a Web application programming interface (API) for a software service. A flow controller executing on the data processing system assigns a queue to each consumer of the software service. Responsive to receiving a current request for the software service from a given consumer of the software service, a flow controller executing on the data processing system adds the current request to a given queue assigned to the given consumer. The flow controller sends a next request from the given queue to the Web API based on a licensed rate of service of the given consumer.

Abstract: A request to activate a software tool can be received, where activation requires a quantity of tokens of a token license model. An entity, project, user-set, user, or combination thereof corresponding to the request can be ascertained. A feature-set to be enabled can be determined by querying preexisting indexed records. The preexisting indexed records can associate different feature-sets to different entities, projects, user-sets, users, or combinations thereof. A token cost can be computed for activating the software tool with the feature-set enabled for the request. Token costs for utilizing the software tool can vary depending upon the enabled feature-set. The computed token cost can be the quantity of tokens required to activate the software tool responsive to the request.

Abstract: A request to activate a software tool can be received, where activation requires a quantity of tokens of a token license model. An entity, project, user-set, user, or combination thereof corresponding to the request can be ascertained. A feature-set to be enabled can be determined by querying preexisting indexed records. The preexisting indexed records can associate different feature-sets to different entities, projects, user-sets, users, or combinations thereof. A token cost can be computed for activating the software tool with the feature-set enabled for the request. Token costs for utilizing the software tool can vary depending upon the enabled feature-set. The computed token cost can be the quantity of tokens required to activate the software tool responsive to the request.

Abstract: A request to activate a software tool can be received, where activation requires a quantity of tokens of a token license model. An entity, project, user-set, user, or combination thereof corresponding to the request can be ascertained. A feature-set to be enabled can be determined by querying preexisting indexed records. The preexisting indexed records can associate different feature-sets to different entities, projects, user-sets, users, or combinations thereof. A token cost can be computed for activating the software tool with the feature-set enabled for the request. Token costs for utilizing the software tool can vary depending upon the enabled feature-set. The computed token cost can be the quantity of tokens required to activate the software tool responsive to the request.

Abstract: A request to activate a software tool can be received, where activation requires a quantity of tokens of a token license model. An entity, project, user-set, user, or combination thereof corresponding to the request can be ascertained. A feature-set to be enabled can be determined by querying preexisting indexed records. The preexisting indexed records can associate different feature-sets to different entities, projects, user-sets, users, or combinations thereof. A token cost can be computed for activating the software tool with the feature-set enabled for the request. Token costs for utilizing the software tool can vary depending upon the enabled feature-set. The computed token cost can be the quantity of tokens required to activate the software tool responsive to the request.