IP Library Granted Patent US 11,556,402
Granted Patent B2
US 11,556,402 · App. 17/159,910 · Granted Jan 17, 2023

Metadata plane for application programming interface

Inventor: Henry Aloysius (Ashburn, VA)
Assignee: Salesforce, Inc.
G06F9/547G06F16/907H04L67/133
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,556,402
App. No.
17/159,910
Granted
Jan 17, 2023
Kind
B2
Abstract

Approaches for data processing are disclosed that include receiving, from a client, an application programming interface (API) request at an API endpoint of an API, where the API endpoint is configured to process data requests at a data plane of the API, identifying, from a header of the API request, a request for metadata associated with the API, redirecting the API request to a metadata plane of the API, retrieving, at the metadata plane of the API, the requested metadata based on the header of the API request, and transmitting, via the API endpoint and to the client, a response message indicating the requested metadata.

Claims (50)

1. A method for data processing at an application server, comprising:

receiving, from a client, an application programming interface (API) request at an API endpoint of an API, wherein the API endpoint is configured to process data requests at a data plane of the API and the API request comprises a request for metadata associated with the API, the metadata comprising configuration metadata associated with the API, real-time metrics associated with the API, or both;

identifying, from a header of the API request, the request for metadata associated with the API;

redirecting the API request to a metadata plane of the API;

retrieving, at the metadata plane of the API, the requested metadata based at least in part on the header of the API request; and

transmitting, via the API endpoint and to the client, a response message indicating the requested metadata.

2. The method of claim 1 , wherein redirecting the API request to the metadata plane of the API further comprises:

transmitting the API request from the data plane of the API to the metadata plane of the API.

3. The method of claim 2 , wherein the API request includes client context information associated with the client.

4. The method of claim 1 , wherein redirecting the API request to the metadata plane of the API further comprises:

intercepting, at a proxy of the data plane of the API, the API request based at least in part on the header of the API request indicating the request for metadata associated with the API.

5. The method of claim 1 , wherein the API request comprises a control message associated with the API, the method further comprising:

controlling a management function of the API based at least in part on the control message.

6. The method of claim 1 , further comprising:

receiving, at the data plane of the API and from the metadata plane of the API, a control message based at least in part on a trigger event.

7. The method of claim 1 , further comprising:

selecting information to be included in the response message based at least in part on an identification of the client in the API request.

8. The method of claim 1 , wherein retrieving, at the metadata plane of the API, the requested metadata further comprises:

consolidating metadata from one or more sources outside the metadata plane of the API; and

storing the consolidated metadata at the metadata plane of the API.

9. The method of claim 1 , wherein at least a portion of the requested metadata is retrieved from a management plane of the API.

10. The method of claim 1 , wherein at least a portion of the requested metadata is stored within the metadata plane of the API.

11. An apparatus for data processing at an application server, comprising:

a processor;

memory coupled with the processor; and

instructions stored in the memory and executable by the processor to cause the apparatus to:

receive, from a client, an application programming interface (API) request at an API endpoint of an API, wherein the API endpoint is configured to process data requests at a data plane of the API and the API request comprises a request for metadata associated with the API, the metadata comprising configuration metadata associated with the API, real-time metrics associated with the API, or both;

identify, from a header of the API request, the request for metadata associated with the API;

redirect the API request to a metadata plane of the API;

retrieve, at the metadata plane of the API, the requested metadata based at least in part on the header of the API request; and

transmit, via the API endpoint and to the client, a response message indicating the requested metadata.

12. The apparatus of claim 11 , wherein the instructions to redirect the API request to the metadata plane of the API are further executable by the processor to cause the apparatus to:

transmit the API request from the data plane of the API to the metadata plane of the API.

13. The apparatus of claim 11 , wherein the instructions to redirect the API request to the metadata plane of the API are further executable by the processor to cause the apparatus to:

intercept, at a proxy of the data plane of the API, the API request based at least in part on the header of the API request indicating the request for metadata associated with the API.

14. The apparatus of claim 11 , wherein the API request comprises a control message associated with the API, and the instructions are further executable by the processor to cause the apparatus to:

control a management function of the API based at least in part on the control message.

15. The apparatus of claim 11 , wherein the instructions are further executable by the processor to cause the apparatus to:

receive, at the data plane of the API and from the metadata plane of the API, a control message based at least in part on a trigger event.

16. The apparatus of claim 11 , wherein the instructions are further executable by the processor to cause the apparatus to:

select information to be included in the response message based at least in part on an identification of the client in the API request.

17. The apparatus of claim 11 , wherein the instructions to retrieve, at the metadata plane of the API, the requested metadata are further executable by the processor to cause the apparatus to:

consolidate metadata from one or more sources outside the metadata plane of the API; and

store the consolidated metadata at the metadata plane of the API.

18. A non-transitory computer-readable medium storing code for data processing at an application server, the code comprising instructions executable by a processor to:

receive, from a client, an application programming interface (API) request at an API endpoint of an API, wherein the API endpoint is configured to process data requests at a data plane of the API and the API request comprises a request for metadata associated with the API, the metadata comprising configuration metadata associated with the API, real-time metrics associated with the API, or both;

identify, from a header of the API request, the request for metadata associated with the API;

redirect the API request to a metadata plane of the API;

retrieve, at the metadata plane of the API, the requested metadata based at least in part on the header of the API request; and

transmit, via the API endpoint and to the client, a response message indicating the requested metadata.

Assignments (2)
CHANGE OF NAME Recorded Dec 18, 2024
From: SALESFORCE.COM, INC.
To: SALESFORCE, INC.
Reel/Frame 069717/0512 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 27, 2021
From: ALOYSIUS, HENRY
To: SALESFORCE.COM, INC.
Reel/Frame 055051/0266 →
Continuity (1)
Related Publication 20220237058A1 · Jul 28, 2022