Salesforce, Inc.

Antonio Garrote

Gaurav Sagar

Patricio Barletta

Javier Isoldi

Matthew Daniel Fuchs

Kelly Henvy

Jonathan Stoikovitch

Luis Contreras

Ezequiel Block

Martin Alejandro Gutierrez

Alejandro Assi

Brian Florentin

Leopoldo Chalub

Gonzalo Guglielmo

Pawel Uchida-Psztyc

Lucas Luppani

Lucas Block

Martin Gutierrez

Pedro Colunga

Pawel Psztyc

Methods, systems, and devices for data processing are described. A federation management service may receive a user selection of a first data source and a second data source via a user interface of the federation management service. The first data source and the second data source may be associated with different data source types. The federation management service may extract schema information from the first data source and the second data source by using source extensions to parse the first data source and the second data source. The federation management service may generate a federated data model by using the schema information to translate the first data source and the second data source into intermediate data sources with a common feature set. Accordingly, the federation management service may generate a target data schema for a federated application programming interface (API) based on the federated data model.

Generating a federated application programming interface for heterogenous data sources

A federation management service may receive, via a user interface of the federation management service, a first user input indicating a selection of a testing environment for testing a federated application programming interface (API). The federation management service may receive, in response to the first user input, a portable binary file for deployment in a web browser of a client host. In some examples, the portable binary file may include a first set of scripts for orchestrating query requests for the federated API and a second set of scripts for orchestrating communications between the web browser of the client host and the first set of scripts. The federation management service may then execute, within the web browser of the client host, a query of the federated API using the first set of scripts and the second set of scripts.

Portable binary files for client side execution of federated application programming interfaces

Methods, systems, apparatuses, devices, and computer program products are described. A mocking service may log a set of real application programming interface (API) data including a set of API requests and corresponding API responses. Using a generator function of a generative adversarial network (GAN), the mocking service may generate a set of sample (e.g., mock) data that mimics the API requests and responses. The mocking service may use a discriminator function to compare the sample data to the real API data and weight parameters of the GAN (e.g., retrain a machine learning model of the GAN) until the generator function generates sample data similar enough to the real API data. When the discriminator function is unable to distinguish the sample data, the real data, the mocking service may store the trained GAN and use it to generate mock API responses to API requests from users.

Sample data generation for a mocking service

Disclosed herein are system, method, and computer program product embodiments for providing an architecture to support a semantic validation technique. The system includes a governance console that carries out data management functionalities to support the validation. Such functionalities include generating, storing and publishing validation profiles that are used by a validation service for validating an asset, a validation reporter that receives and stores validation reports and performs notification functions to notify relevant individuals of the validation results, as well as a profile runner and associations manager that directly support the validation service.

API governance enforcement architecture

A system allows translation across API models represented using different API description languages. The system stores model bindings from a common visualization model format to multiple API description languages. The model bindings map constructs of the API description language to and from modeling constructs of the common visualization model format. The system uses the model bindings to convert API models to and from representations based on API description languages to the common visualization model format. The system used the common visualization model format to generate visualizations of the API model that can be displayed via a user interface and also allow users to modify the API model.

Extensible binding mechanism for translating between application programming interface description languages

A federation management service may generate a federated application program interface (API) based on multiple data sources. The federation management service may detect changes to one or more of the multiple data sources, which may result in generation of a new version of the federated API. The changes to the data sources may be documented in a change event log. The change event log may be used to recreate a prior version of the federated API by applying changes of the change event log to a federated schema corresponding to the federated API. A snapshotting technique may capture the state of the federated schema at various points in time, and snapshots may be used to regenerate a prior version of the federated API using the change events of the change event log.

Regeneration audit log

Methods, apparatuses, and computer-program products are disclosed. The method may include deploying a runtime agent onto a private compute architecture for running one or more federated application programming interfaces (APIs) on the private compute architecture. The method may include receiving, via a user interface of a federation management service, user input to manage an operation of the one or more federated APIs, where the federation management service is hosted on public cloud-based resources. The method may include communicating, based on the user input, control signaling between the runtime agent and a runtime manager that is hosted on a control plane of the federation management service in the public cloud-based resources.

Deployed application programming interface management

Methods, systems, and devices for data processing are described. The method may include generating a federated application programming interface (API) from a plurality of data sources. One or more of the plurality of data sources may include an annotated data schema that defines one or more API endpoints for performing a distributed mutation of the plurality of data sources according to a supported distributed transaction protocol. The method may include receiving, via a single call to a single field of the federated API, a request at the federated API to perform a distributed mutation on the plurality of data sources. The method may include orchestrating, via a federation management service and the one or more API endpoints, a plurality of mutation calls to the plurality of data sources according to the distributed transaction protocol.

Federated distributed mutation

Techniques are disclosed relating to the serialization of data of a database. A computer system may maintain a database that stores data as a plurality of triples. A triple may include a first data entity that is connected to a second data entity via an edge, and triples of the plurality of triples may be connected to form graphs. The computer system may store metadata defining types of edges between data entities. An edge's type may indicate a procedure for serializing a target data entity connected to that edge's type. The computer system may receive a request to access a data entity associated with a plurality of descendant data entities connected to the data entity via edges. The computer system may generate an output having the data entity and one or more of the plurality of descendant data entities that are serialized according to the types of edges.

Mechanisms for serializing triples of a database store

Disclosed herein are system, method, and computer program product embodiments for incorporating metadata extensions of various metadata formats into a metadata mapping or graphing function. Extensions for various formats are separately defined with a predetermined syntax. When a metadata object is received, it is scanned to determine whether any extensions are present. When such an extension is detected, the parser is loaded with an extension parsing plugin corresponding to the format of the metadata object. That plugin retrieves extension definitions from a repository in order to accurately parse the extension information of the metadata object. The metadata object and its extensions can then be parsed and graphed accordingly.

System and method for semantic metadata extensions in API governance using validation rulesets

Methods, apparatuses, and computer program products for feature based application programming interface (API) federation are disclosed. In some examples, a federated API manager may receive user input indicating source APIs including features for data processing. The federated API manager may identify elements forming one or more patterns from the features based on federation protocols. The federated API manager may identify federated operations based on the identified elements and federation operation rules. The federated API manager may generate a federated API schema based on the federated operation rules, and the federated API schema may expose the federated operations.

Growing community of inventors

San Francisco, CA, United States of America

Antonio Garrote