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, 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: 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: 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: 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: 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 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. 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: 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 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: A GraphQL server stores schemas for GraphQL APIs in a schema store, the schemas defining operations, types and fields of the APIs. Field resolvers are associated with the fields of the APIs to specify which of the data source is to be used to fulfill an API query request. When an event is detected that makes changes to a schema of any of the data sources, the schema store is accessed and an old field name is automatically replaced with a new field name in both the retrieved schemas and the field resolvers mapped to the retrieved schemas. Responsive to receiving an API request, it is determined whether the request has any field names that do not match the corresponding schema, and if so, the old field name is replaced with the new field name in the request.

Abstract: A GraphQL server stores schemas for GraphQL APIs in a schema store, the schemas defining operations, types and fields of the APIs. Field resolvers are associated with the fields of the APIs to specify which of the data source is to be used to fulfill an API query request. When an event is detected that makes changes to a schema of any of the data sources, the schema store is accessed and an old field name is automatically replaced with a new field name in both the retrieved schemas and the field resolvers mapped to the retrieved schemas. Responsive to receiving an API request, it is determined whether the request has any field names that do not match the corresponding schema, and if so, the old field name is replaced with the new field name in the request.

Abstract: Technologies are provided for identifying problems with network monitoring agents. For example, a network monitoring agent that is experiencing network packet loss can be examined to determine if it is degraded. For example, metrics can be obtained that are associated with the network monitoring agent. The obtained metrics can then be evaluated against thresholds. For example, if a high confidence metric is outside of a threshold for the high confidence metric, then a determination can be made that the network monitoring agent is degraded. As another example, if two low confidence metrics are outside of respective thresholds, then a determination can be made that the network monitoring agent is degraded. If a network monitoring agent is degraded, then its monitoring data can be discarded.

Abstract: In one embodiment, detection of failures in a network device can be achieved by obtaining a last hop of partial traceroutes. For example, the last hops of the partial traceroutes detected in a time period can be sorted by frequency of occurrence. Multiple clusters can be generated, one with last hops that are most frequent and at least one other with the last hops that are less frequent. The hop with the highest frequency and the last hop with the second highest frequency can be compared. If the last hop with the highest frequency exceeds the second highest frequency by a predetermined amount, then the last hop with the highest frequency is alarmable.