Granted Patent B2

US 12,498,995 · App. 17/881,250 · Granted Dec 16, 2025

Inventors: Gaurav Sagar (Bellevue, WA); Antonio Garrote (San Francisco, CA); Patricio Barletta (Brentwood, CA); Javier Isoldi (Buenos Aires, AR); Gonzalo Guglielmo (Buenos Aires, AR); Leopoldo Chalub (Buenos Aires, AR)

Assignee: Salesforce, Inc.

G06F9/544G06F16/27

Abstract

Claims (50)

1 . A method for data processing, comprising:

receiving, via a user interface of a federation management service, a user selection of a first data source associated with a first data source type corresponding to a first application programming interface (API) and a second data source associated with a second data source type corresponding to a second API, wherein the second data source type is different from the first data source type and the second API is different from the first API;

extracting schema information from the first data source that corresponds to the first API and the second data source that corresponds to the second API by using one or more source extensions to parse the first data source and the second data source, the schema information from the first data source indicating a first capability feature set supported by the first data source that indicates a first set of operations that the first data source is capable of performing and the schema information from the second data source indicating a second capability feature set supported by the second data source that indicates a second set of operations that the second data source is capable of performing, wherein the second capability feature set supported by the second data source is different from the first capability feature set supported by the first data source based at least in part on at least one operation within the first set of operations of the first capability feature set that is supported by the first data source being unsupported by the second data source;

translating the schema information from the first data source that corresponds to the first API into a first intermediate data source and the schema information from the second data source that corresponds to the second API into a second intermediate data source, wherein translating the schema information from the first data source into the first intermediate data source and translating the schema information from the second data source into the second intermediate data source comprises removing one or more capability features from the first capability feature set supported by the first data source to generate a common capability feature set for the first intermediate data source and the second intermediate data source that is supported by the federation management service, the first data source, and the second data source, wherein the common capability feature set indicates a common set of operations that the federation management service, the first data source, and the second data source are capable of performing, and wherein the one or more capability features removed are associated with the at least one operation within the first set of operations of the first capability feature set that is supported by the first data source and unsupported by the second data source;

generating a federated data model by integrating the first intermediate data source with the second intermediate data source based at least in part on translating the schema information from the first data source into the first intermediate data source and translating the schema information from the second data source into the second intermediate data source including the removal of the one or more capability features from the first capability feature set to generate the common capability feature set for the first intermediate data source and the second intermediate data source that is supported by the federation management service, wherein generation of the federated data model further comprises a generation of a semantic graph representation and an extended graph representation of the first intermediate data source and the second intermediate data source using a parsing plug-in that interfaces with the one or more source extensions; and

generating a target data schema for a federated API that provides access to both the first data source that corresponds to the first API and the second data source that corresponds to the second API, wherein the target data schema for the federated API is generated based at least in part on the federated data model that includes an integration of the first intermediate data source and the second intermediate data source.

2 . The method of claim 1 , further comprising:

obtaining metadata associated with a first data schema of the first data source that corresponds to the first API and a second data schema of the second data source that corresponds to the second API, wherein generating the target data schema for the federated API is based at least in part on the metadata.

3 . The method of claim 1 , further comprising:

receiving, via the user interface of the federation management service, a user input that comprises one or more metadata annotations associated with the first data source that corresponds to the first API and the second data source that corresponds to the second API, wherein generating the target data schema for the federated API is based at least in part on the one or more metadata annotations.

4 . The method of claim 1 , further comprising:

receiving, via the user interface of the federation management service, a query related to one or more data objects from the first data source that corresponds to the first API or the second data source that corresponds to the second API; and

retrieving query results associated with the one or more data objects by using the federated API to access one or both of the first data source or the second data source.

5 . The method of claim 4 , further comprising:

transmitting, for display at the user interface of the federation management service, an indication of the query results associated with the one or more data objects.

6 . The method of claim 4 , further comprising:

retrieving schema version information and run-time information associated with one or both of the first data source that corresponds to the first API or the second data source that corresponds to the second API, wherein the federated API uses the schema version information and the run-time information to access one or both of the first data source that corresponds to the first API or the second data source that corresponds to the second API.

7 . The method of claim 1 , wherein generating the federated data model comprises:

mapping a first set of capability features supported by the first data source that corresponds to the first API and a second set of capability features supported by the second data source that corresponds to the second API to the common capability feature set supported by the federation management service, the first data source, and the second data source.

8 . The method of claim 1 , wherein the common capability feature set supported by the federation management service, the first data source, and the second data source, includes read operations, write operations, pagination operations, streaming operations, or a combination thereof.

9 . The method of claim 1 , wherein the first data source that corresponds to the first API and the second data source that corresponds to the second API have different capability feature sets and different API formats.

10 . The method of claim 1 , wherein one or both of the first API or the second API comprise a Representational State Transfer API, a Graph Query Language API, or an AsyncAPI.

11 . An apparatus for data processing, comprising:

one or more processors;

one or more memories coupled with the one or more processors; and

instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to:

receive, via a user interface of a federation management service, a user selection of a first data source associated with a first data source type corresponding to a first application programming interface (API) and a second data source associated with a second data source type corresponding to a second API, wherein the second data source type is different from the first data source type and the second API is different from the first API;

extract schema information from the first data source that corresponds to the first API and the second data source that corresponds to the second API by using one or more source extensions to parse the first data source and the second data source, the schema information from the first data source indicating a first capability feature set supported by the first data source that indicates a first set of operations that the first data source is capable of performing and the schema information from the second data source indicating a second capability feature set supported by the second data source that indicates a second set of operations that the second data source is capable of performing, wherein the second capability feature set supported by the second data source is different from the first capability feature set supported by the first data source based at least in part on at least one operation within the first set of operations of the first capability feature set that is supported by the first data source being unsupported by the second data source;

translate the schema information from the first data source that corresponds to the first API into a first intermediate data source and the schema information from the second data source that corresponds to the second API into a second intermediate data source, wherein translating the schema information from the first data source into the first intermediate data source and translating the schema information from the second data source into the second intermediate data source comprises removing one or more capability features from the first capability feature set supported by the first data source to generate a common capability feature set for the first intermediate data source and the second intermediate data source that is supported by the federation management service, the first data source, and the second data source, wherein the common capability feature set indicates a common set of operations that the federation management service, the first data source, and the second data source are capable of performing, and wherein the one or more capability features removed are associated with the at least one operation within the first set of operations of the first capability feature set that is supported by the first data source and unsupported by the second data source;

generate a federated data model by integrating the first intermediate data source with the second intermediate data source based at least in part on translating the schema information from the first data source into the first intermediate data source and translating the schema information from the second data source into the second intermediate data source including the removal of the one or more capability features from the first capability feature set to generate the common capability feature set for the first intermediate data source and the second intermediate data source that is supported by the federation management service, wherein generation of the federated data model further comprises a generation of a semantic graph representation and an extended graph representation of the first intermediate data source and the second intermediate data source using a parsing plug-in that interfaces with the one or more source extensions; and

generate a target data schema for a federated API that provides access to both the first data source that corresponds to the first API and the second data source that corresponds to the second API, wherein the target data schema for the federated API is generated based at least in part on the federated data model that includes an integration of the first intermediate data source and the second intermediate data source.

12 . The apparatus of claim 11 , wherein the instructions are further executable by the one or more processors to cause the apparatus to:

obtain metadata associated with a first data schema of the first data source that corresponds to the first API and a second data schema of the second data source that corresponds to the second API, wherein generating the target data schema for the federated API is based at least in part on the metadata.

13 . The apparatus of claim 11 , wherein the instructions are further executable by the one or more processors to cause the apparatus to:

receive, via the user interface of the federation management service, a user input that comprises one or more metadata annotations associated with the first data source that corresponds to the first API and the second data source that corresponds to the second API, wherein generating the target data schema for the federated API is based at least in part on the one or more metadata annotations.

14 . The apparatus of claim 11 , wherein the instructions are further executable by the one or more processors to cause the apparatus to:

receive, via the user interface of the federation management service, a query related to one or more data objects from the first data source that corresponds to the first API or the second data source that corresponds to the second API; and

retrieve query results associated with the one or more data objects by using the federated API to access one or both of the first data source or the second data source.

15 . The apparatus of claim 14 , wherein the instructions are further executable by the one or more processors to cause the apparatus to:

transmit, for display at the user interface of the federation management service, an indication of the query results associated with the one or more data objects.

16 . The apparatus of claim 14 , wherein the instructions are further executable by the one or more processors to cause the apparatus to:

retrieve schema version information and run-time information associated with one or both of the first data source that corresponds to the first API or the second data source that corresponds to the second API, wherein the federated API uses the schema version information and the run-time information to access one or both of the first data source that corresponds to the first API or the second data source that corresponds to the second API.

17 . The apparatus of claim 11 , wherein the instructions to generate the federated data model are executable by the one or more processors to cause the apparatus to:

map a first set of capability features supported by the first data source that corresponds to the first API and a second set of capability features supported by the second data source that corresponds to the second API to the common capability feature set supported by the federation management service, the first data source, and the second data source.

18 . A non-transitory computer-readable medium storing code for data processing, the code comprising instructions executable by one or more processors to:

receive, via a user interface of a federation management service, a user selection of a first data source associated with a first data source type corresponding to a first application programming interface (API) and a second data source associated with a second data source type corresponding to a second API, wherein the second data source type is different from the first data source type and the second API is different from the first API;

extract schema information from the first data source that corresponds to the first API and the second data source that corresponds to the second API by using one or more source extensions to parse the first data source and the second data source, the schema information from the first data source indicating a first capability feature set supported by the first data source that indicates a first set of operations that the first data source is capable of performing and the schema information from the second data source indicating a second capability feature set supported by the second data source that indicates a second set of operations that the second data source is capable of performing, wherein the second capability feature set supported by the second data source is different from the first capability feature set supported by the first data source based at least in part on at least one operation within the first set of operations of the first capability feature set that is supported by the first data source being unsupported by the second data source;

translating the schema information from the first data source that corresponds to the first API into a first intermediate data source and the schema information from the second data source that corresponds to the second API into a second intermediate data source, wherein translating the schema information from the first data source into the first intermediate data source and translating the schema information from the second data source into the second intermediate data source comprises removing one or more capability features from the first capability feature set supported by the first data source to generate a common capability feature set for the first intermediate data source and the second intermediate data source that is supported by the federation management service, the first data source, and the second data source, wherein the common capability feature set indicates a common set of operations that the federation management service, the first data source, and the second data source are capable of performing, and wherein the one or more capability features removed are associated with the at least one operation within the first set of operations of the first capability feature set that is supported by the first data source and unsupported by the second data source;

generating a federated data model by integrating the first intermediate data source with the second intermediate data source based at least in part on translating the schema information from the first data source into the first intermediate data source and translating the schema information from the second data source into the second intermediate data source including the removal of the one or more capability features from the first capability feature set to generate the common capability feature set for the first intermediate data source and the second intermediate data source that is supported by the federation management service, wherein generation of the federated data model further comprises a generation of a semantic graph representation and an extended graph representation of the first intermediate data source and the second intermediate data source using a parsing plug-in that interfaces with the one or more source extensions; and

generate a target data schema for a federated API that provides access to both the first data source that corresponds to the first API and the second data source that corresponds to the second API, wherein the target data schema for the federated API is generated based at least in part on the federated data model that includes an integration of the first intermediate data source and the second intermediate data source.

Assignments (1)

Continuity (1)

References Cited (35)