Selectively exposing Application Programming Interfaces dynamically for microservices

Patent metadata

Field	Value
Publication number	US-2022083407-A1
Application number	US-202017084091-A
Country	US
Kind code	A1
Filing date	Oct 29, 2020
Priority date	Sep 16, 2020
Publication date	Mar 17, 2022
Grant date	—

Abstract

Systems and methods for selectively exposing Application Programming Interfaces (APIs) dynamically and in a scalable manner include, when a new API is exposed in a microservice, making it accessible via a gateway if it is indicated to be exposed. The present disclosure focused on exposing a range of services behind the API gateway in a scalable, easy to use manner. The present disclosure includes an API gateway that supports a new microservice easily and efficiently as long as it provides metadata. The API gateway dynamically decides which APIs will be exposed via the gateway with filtering per service. Also, the API gateway routes any request made by a user to the gateway back to the intended microservice in a transparent fashion, as well as performing any additional transformations of the request before sending it back to the microservice.

First claim

What is claimed is:

1 . A non-transitory computer-readable storage medium having computer-readable code stored thereon for programming one or more processors to perform steps of:
receiving Application Programming Interface (API) metadata from one or more microservices; selectively exposing APIs associated with the one or more microservices to a user based on the API metadata; and routing a request from the user to an intended microservice in a transparent fashion to the user.

2 . The non-transitory computer-readable storage medium of claim 1 , wherein the steps further include
transforming the request from the user prior to routing to the intended microservice; and transforming a response from the intended microservice prior to sending back to the user.

3 . The non-transitory computer-readable storage medium of claim 2 , wherein the transforming the request includes changing a first term in the request to a second term for the microservice, and wherein the transforming the response includes changing the second term in the response to the first term.

4 . The non-transitory computer-readable storage medium of claim 1 , wherein the selectively exposing the APIs is based on filtering for the one or more microservices.

5 . The non-transitory computer-readable storage medium of claim 4 , wherein the filtered APIs are any of not fully supported and internal only.

6 . The non-transitory computer-readable storage medium of claim 4 , wherein the filtering is based on tags added in the API metadata.

7 . The non-transitory computer-readable storage medium of claim 1 , wherein the routing the request is performed without validating the request such that the intended microservice performs validation.

8 . A method comprising:
receiving Application Programming Interface (API) metadata from one or more microservices; selectively exposing APIs associated with the one or more microservices to a user based on the API metadata; and routing a request from the user to an intended microservice in a transparent fashion to the user.

9 . The method of claim 8 , further comprising
transforming the request from the user prior to routing to the intended microservice; and transforming a response from the intended microservice prior to sending back to the user.

10 . The method of claim 9 , wherein the transforming the request includes changing a first term in the request to a second term for the microservice, and wherein the transforming the response includes changing the second term in the response to the first term.

11 . The method of claim 8 , wherein the selectively exposing the APIs is based on filtering for the one or more microservices.

12 . The method of claim 11 , wherein the filtered APIs are any of not fully supported and internal only.

13 . The method of claim 11 , wherein the filtering is based on tags added in the API metadata.

14 . The method of claim 8 , wherein the routing the request is performed without validating the request such that the intended microservice performs validation.

15 . An apparatus comprising:
one or more processors and memory comprising instructions that, when executed, cause the one or more processors to
receive Application Programming Interface (API) metadata from one or more microservices;
selectively expose APIs associated with the one or more microservices to a user based on the API metadata; and
route a request from the user to an intended microservice in a transparent fashion to the user.

16 . The apparatus of claim 15 , wherein the instructions further cause the one or more processors to
transform the request from the user prior to routing to the intended microservice; and transform a response from the intended microservice prior to sending back to the user.

17 . The apparatus of claim 16 , wherein the request is transformed by changing a first term in the request to a second term for the microservice, and wherein the response is transformed by changing the second term in the response to the first term.

18 . The apparatus of claim 15 , wherein the APIs are selectively exposed based on filtering for the one or more microservices.

19 . The apparatus of claim 18 , wherein the filtered APIs are any of not fully supported and internal only.

20 . The apparatus of claim 18 , wherein the filtering is based on tags added in the API metadata.

Assignees

• Zscaler Inc

Inventors

• Nadendla Arvind
• Srinivasan Subramanian
• Dhiman Vivek

Classifications

• G06F9/547 Primary

  Remote procedure calls [RPC]; Web services · CPC title

• G06F9/5011

  the resources being hardware resources other than CPUs, Servers and Terminals · CPC title

• G06F9/4881

  Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues · CPC title