Salesforce Com, Inc.

Salesforce, Inc.

Reuben Cornel

Samarpan Jain

Jan Asita Fernando

Jonathan Bruce

Brian Esserlieu

Jay Hurst

Brian Jaffery Tajuddin

Siddhi Mehta

Richard Perry Pack, Iii

Stefan Derdak

Hormoz Tarevern

Techniques and architectures for data ingestion in an environment having a distributed data storage system. A request to import data into the environment. The data to be imported from an external source through an application programming interface (API). The request is analyzed to determine if the request corresponds to a request to import a large data load. The data is staged if the request is for the large data load. Data management jobs are created to cause the data to be stored in one or more nodes of the distributed data storage system. The data management jobs are transmitted to corresponding nodes in the distributed data storage system. The jobs are executed asynchronously to cause the data to be stored in the nodes.

Techniques and architectures for importation of large data load

Big object bulk data ingest

A method is provided for orchestrating a workflow. In some embodiments, the method includes executing a workflow including a first controller that includes a first callout function and a first callback function and corresponds to a first microservice. Execution of the workflow includes execution of the first callout function that causes invocation of the first call to the first microservice. The method further includes receiving a notification of an execution state from the first microservice and transmitting the execution state to the first callback function. The method also includes in response to transmitting the execution state to the first callback function, receiving a function output based on the execution state from the first callback function. The method further includes determining, based on the function output, whether to execute a subsequent controller. The method also includes in response to a determination to execute the subsequent controller, executing the subsequent controller.

Orchestration of a sequence of computations by external systems

Methods and systems are provided for turning on and off features at run time. The method includes providing a unique enabling predicate (e.g., an 'if enabled' statement) for one or more executable features (blocks of code), configuring a permissions library, and caching the configured permissions library. The method further includes interrogating the cache with the first 'if enabled' predicate, executing the block of code (feature) if the cache yields &#x201c;true&#x201d; for the requesting user, and not executing the code block if the cache yields &#x201c;false&#x201d; for the requesting user.

System and method for controlling the on and off state of features at runtime

Growing community of inventors

San Francisco, CA, United States of America

Reuben Cornel