Abstract: 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.

Abstract: Methods, systems, apparatuses, devices, and computer program products are described. A mapping service may receive a user input indicating conditions for generating mock data values into application programming interface (API) fields. The mapping service may map a set of API fields to a set of mock collection library (MCL) fields using a mapping scheme. For example, the mapping service may map field names or descriptions of the API and MCL fields based on similarity scores determined using word embeddings. The mapping service may display a set of mapped fields and example mock data to a user. If the user rejects the mapped fields, the mapping service may remap the fields. Once the user accepts the mapped fields, the mapping service may generate a full set of mock data for the API (e.g., mock API responses to an API request) and store the mapping scheme.

Abstract: 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.

Abstract: A federation management service may receive an indication of multiple data sources to integrate into a federated application programming interface (API). One of the data sources is a database that is associated with an API schema that includes annotations that map elements of the API schema to the features of the database. The federation management services processes the API schema to generate the federated API. The federated API may receive a request for an element that is mapped to the feature of the database, generate a query based on the annotations of the API schema, and return a result based on the generated query.

Abstract: 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.

Abstract: Methods, systems, and devices for data processing are described. A federation management service may receive a user input indicating multiple data sources as federation inputs into federated application programming interface (API). The one or more data sources may have a first metadata input that defines a target schema for a computed field and a second metadata input that defines a transformation for computing a value for the computed field from a data source schema to the target schema for the computed field. A runtime service of the federation management service may compute the value of the computed field using the second metadata input. The federation management service may generate the federated API from the data sources, where the federated API includes the computed field.

Abstract: 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.

Abstract: 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.

Abstract: A computing system may support a federation management service that receives an input indicating a plurality of data sources comprising one or more tags corresponding to one or more elements of the plurality of data sources. The federation management service may generate a federated application programming interface (API) using the data sources, and the federated API may include elements of the data sources. The federation management service may receive a second user input selecting a set of tags for exclusion or inclusion of elements in a subgraph of the federated API. The federation management service may generate the subgraph that includes a subset of the one or more elements of the plurality of data sources.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: Techniques are disclosed relating to the garbage collection of data of a database. A computer system may maintain a database that stores data as a plurality of triples. A given 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 a plurality of graphs. The computer system may store metadata that defines strengths of edges between graphs of the plurality of graphs. The computer system may receive a request to delete a particular triple or graph of the plurality of graphs. The particular graph may include a set of edges originating in the particular graph to other graphs of the plurality of graphs. The computer system may determine, based on the stored metadata, which graphs of the other graphs to delete in addition to the particular graph.

Abstract: 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.

Abstract: 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.

Abstract: Disclosed herein are system, method, and computer program product embodiments for facilitating access to and incorporation of APIs within an application during development, while ensuring that the API satisfies quality constraints. These quality constraints are controlled by the application of rules, which result in a maturity score for the API, in accordance with embodiments. These rules may be provided by a variety of sources for use in scoring the API at various stages. For example, a developer group may control access to developers within the group by applying a ruleset that restricts APIs for applications written by the developer group to a threshold score. This threshold score can limit or restrict APIs that are offered to a developer by an API exchange. Additionally, a ruleset may be applied to enforce a minimum score for submission of an API for inclusion within an API exchange.

Abstract: 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.

Abstract: Disclosed herein are system, method, and computer program product embodiments for validating resources within an IT system using a syntax agnostic validation mechanism. Metadata objects describing a resource may be generated by multiple processes in the IT system and be of different metadata formats. These metadata objects may be parsed into a unified semantic graph over which validation rules may be applied. The semantic graph and a validation ruleset comprising one or more validation rules may be input into a validation engine. The validation engine may interpret the validation into logical assertions then apply them over the semantic graph. The validation engine may then generate a validation report indicating whether the graph is conformant. The validation report may include information about any validation failures that may have occurred and may be displayed to a user on a client device via a graphical user interface.

Abstract: 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.

Abstract: 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.