Salesforce Com, Inc.

Salesforce, Inc.

Richard Perry Pack, Iii

Benjamin Carl Snyder

Sachin Desai

Matthew Francis Davidchuk

Qingqing Liu

Philip Norman Calvin

Walter Macklem

Igor A Shmulevich

Kevin Venkiteswaran

David M Brady

Reuben Cornel

Stefan Derdak

Hormoz Tarevern

Phillip Norman Calvin

To deliver up-to-date, coherent user data to applications upon request, the disclosed technology includes systems and methods for caching data and metadata after it has been synchronously loaded&#x2014;for future retrieval with a page load time close to zero milliseconds. To provide this experience, data needs to be stored as locally to a user as possible, in the cache on the local device or in an edge cache located geographically nearby, for use in responding to requests. Applications which maintain caches of API results can be notified of their invalidation, and can detect the invalidation, propagate the invalidation to any further client tiers with the appropriate derivative type mapping, and refresh their cached values so that clients need not synchronously make the API requests again&#x2014;ensuring that the client has access to the most up-to-date copy of data as inexpensively as possible&#x2014;in terms of bandwidth and latency.

Invalidation and refresh of multi-tier distributed caches

To deliver up-to-date, coherent user data to applications upon request, the disclosed technology includes systems and methods for caching data and metadata after it has been synchronously loaded&#x2014;for future retrieval with a page load time close to zero milliseconds. To provide this experience, data needs to be stored as locally to a user as possible, in the cache on the local device or in an edge cache located geographically nearby, for use in responding to requests. Applications which maintain caches of API results can be notified of their invalidation, and can detect the invalidation, propagate the invalidation to any further client tiers with the appropriate derivative type mapping, and refresh their cached values so that clients need not synchronously make the API requests again&#x2014;insuring that the client has access to the most up-to-date copy of data as inexpensively as possible&#x2014;in terms of bandwidth and latency.

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

Reducing latency by caching derived data at an edge server

The technology disclosed describes systems and methods for optimizing delivery of form factor specific content for users in different environments, such as desktop computer browsers and mobile device applications. The technology further discloses systems and methods for providing support for developers whose goal is to render specific implementations of a user interface to deliver distinct user interface experiences.

Systems and methods of optimizing delivery of form factor specific content

Disclosed are examples of systems, apparatus, methods and computer program products for delegating handling of computing events of a mobile device application. For example, an identification of a computing event can be received. The computing event can have associated metadata. The computing event can be associated with a first component of a plurality of components of a first application executable on a mobile device. The plurality of components can comprise at least a native component and a web browser component. One or more rules can be applied to the metadata. Based on the application of the one or more rules to the metadata, a second component can be identified for handling the event. Handling of the event can be delegated to the second component.

Delegating handling of computing events of a mobile device application

A hierarchical template framework may include lower tier templates that identify groups of software components for discrete software services. The template framework also may include upper tier templates that include one or more lower tier templates and identify software components for a prearranged group of the software services configured to support and operate with an associated category of core software functions. A software developer may build a software application from the software components identified in a selected upper tier template, lower tier templates, and any other core software components identified for the core software functions. The templates prevent the software developer from having to manually locate and test all of the software components for different software services used in a software application.

Template based software container

In accordance with disclosed embodiments, there are provided systems and methods for implementing a uniform application user interface across a hosted computing environment, such as an on-demand or cloud computing environment which utilizes multi-tenant database technologies, client-server technologies, traditional database technologies, or other computing architecture in support of the hosted computing environment. According to a particular embodiment such a system includes a processor and a memory to execute instructions at the system; a foundation layer to define a plurality of components; the plurality of components, each to define one or more features to be consumed by an arbitrary application built from the features; wherein the one or more features are to each incorporate one or more of the components defined by the foundation layer and further wherein each of the one or more features have visibility to one or more interfaces available for the respective features to connect with but have no visibility to or about any arbitrary application that will consume them; a glue logic layer to link the features to the arbitrary application built from the features, wherein the arbitrary application built from the features has a one-way view of the features consumed through the glue logic layer without permitting the features visibility to or about the arbitrary application built; and wherein the arbitrary application built from the features is to execute within the host organization. Other related embodiments are disclosed.

Growing community of inventors

San Francisco, CA, United States of America

Richard Perry Pack, Iii