Servicenow, Inc.

Matthew Stoddart

Pankaj Puniani

Harry Thomas Nelson

Rebecca Anita Dias

Joshua Timothy Nerius

David Tamjidi

Venkata Kiran Kumar Koya

Silas Andrew Smith

Stuart Dean Swope

Bryan Mather Barnard

Amila Chinthaka Suriarachchi

Kyle James Barron-Kraus

Lubomir Kostadinov Vardin

Francis Van Aeken

Wei Rui

A computing system includes a server. The server is communicatively coupled to a data repository and is configured to store a data in the data repository. The server is further configured to create, via a visual information flow creation tool, at least one information flow object, wherein the at least one information flow object comprises a flow, a sub-flow, an Action, or a combination thereof. The server is also configured to interface with the at least one information flow object via a front-end application programing interface (API), a back-end API, or a combination thereof. The server is additionally configured to execute the at least one information flow object via the front-end API, the back-end API, or a combination thereof, and to retrieve results obtained by executing the at least one information flow object via the front-end API, the back-end API, or the combination thereof.

System and method for workflow application programming interfaces (APIS)

The present disclosure relates to systems and methods of implementing rate limiting in a representational state transfer (REST) application programming interface (API) system. A method of operating an instance of a REST API server, includes: receiving a REST API request that matches a rate limit rule associated with the instance of the REST API server; preparing a REST API response that includes rate limiting response headers. The method includes determining whether a rate limit violation exists that corresponds to the rate limit rule and, when it does, adding an error message to the REST API response. Otherwise, the REST API request is fulfilled and corresponding data is added to the REST API response. The method includes sending the REST API response including the rate limiting response headers and either the error message or the corresponding data.

Systems and methods of rate limiting for a representational state transfer (REST) application programming interface (API)

In accordance with the present approach, concurrent processing is employed to facilitate a data import process. By way of example, in accordance with the present approach, local or external data to be imported is partitioned into multiple, separate import sets. In the subsequent stage, the import sets are processed concurrently to populate the target table.

Concurrent data imports

A computing system includes a server. The server is communicatively coupled to a data repository and is configured to store a data in the data repository. The server is further configured to create, via a visual information flow creation tool, at least one information flow object, wherein the at least one information flow object comprises a flow, a sub-flow, an Action, or a combination thereof. The server is also configured to interface with the at least one information flow object via a front-end application programming interface (API), a back-end API, or a combination thereof. The server is additionally configured to execute the at least one information flow object via the front-end API, the back-end API, or a combination thereof, and to retrieve results obtained by executing the at least one information flow object via the front-end API, the back-end API, or the combination thereof.

A computing system may be configured to store a master session context of a HyperText Transfer Protocol (HTTP) session, and a queue of HTTP transactions. A middleware module of the computing system may be executable by the processor to: (i) select a first HTTP transaction from the queue, (ii) execute an exclusive phase of the first HTTP transaction, including copying the master session context into a first local session context, (iii) cause a web server to execute a non-exclusive phase of the first HTTP transaction using a first thread and the first local session context, (iv) select a second HTTP transaction from the queue, and (v) execute an exclusive phase of the second HTTP transaction, including copying the master session context into a second local session context. Execution of the exclusive phase of the second HTTP transaction and the execution of the non-exclusive phase of the first HTTP transaction occur concurrently.

Scheduling and concurrent processing of protocol transactions

Growing community of inventors

San Diego, CA, United States of America

Matthew Stoddart