Caching framework for a multi-tenant identity and data security management cloud service
First Claim
1. A non-transitory computer readable medium having instructions stored thereon that, when executed by one or more processors, cause the processors to provide cloud-based identity and access management, the providing comprising:
- receiving a request from a client for a resource, the request comprising a call to a first Application Programming Interface (API) that identifies a first microservice, the resource comprising metadata;
authenticating the request;
accessing the first microservice of a plurality of microservices based on the request, the first microservice comprising a remote API proxy and a near cache, wherein the near cache is local to the first microservice and fronts a remote cache;
determining, by the remote API proxy, whether the resource is indicated as cacheable based on the metadata, and if cacheable whether the resource is cached in the near cache or in the remote cache, wherein the remote cache is external of the first microservice and the remote API proxy establishes a connection with the remote cache;
in response to determining the resource is indicated as cacheable in the near cache, retrieving the resource from the near cache or from the remote cache when the resource is cached;
calling an administration microservice to obtain the resource when the resource is not cached, wherein the administration microservice is a different microservice than the first microservice; and
providing the resource to the client.
1 Assignment
0 Petitions
Accused Products
Abstract
A system provides cloud-based identity and access management. The system receives a request from a client for a resource, authenticates the request, and accesses a microservice based on the request. The system determines, by the microservice, whether the resource is cached in a near cache or in a remote cache, retrieves the resource from the near cache or from the remote cache when the resource is cached, and calls an administration microservice to obtain the resource when the resource is not cached. The system then provides the resource to the client.
-
Citations
20 Claims
-
1. A non-transitory computer readable medium having instructions stored thereon that, when executed by one or more processors, cause the processors to provide cloud-based identity and access management, the providing comprising:
-
receiving a request from a client for a resource, the request comprising a call to a first Application Programming Interface (API) that identifies a first microservice, the resource comprising metadata; authenticating the request; accessing the first microservice of a plurality of microservices based on the request, the first microservice comprising a remote API proxy and a near cache, wherein the near cache is local to the first microservice and fronts a remote cache; determining, by the remote API proxy, whether the resource is indicated as cacheable based on the metadata, and if cacheable whether the resource is cached in the near cache or in the remote cache, wherein the remote cache is external of the first microservice and the remote API proxy establishes a connection with the remote cache; in response to determining the resource is indicated as cacheable in the near cache, retrieving the resource from the near cache or from the remote cache when the resource is cached; calling an administration microservice to obtain the resource when the resource is not cached, wherein the administration microservice is a different microservice than the first microservice; and providing the resource to the client. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. A method of providing cloud-based identity and access management, comprising:
-
receiving a request from a client for a resource, the request comprising a call to a first Application Programming Interface (API) that identifies a first microservice, the resource comprising metadata; authenticating the request; accessing the first microservice of a plurality of microservices based on the request, the first microservice comprising a remote API proxy and a near cache, wherein the near cache is local to the first microservice and fronts a remote cache; determining, by the remote API proxy, whether the resource is indicated as cacheable based on the metadata, and if cacheable whether the resource is cached in the near cache or in the remote cache, wherein the remote cache is external of the first microservice and the remote API proxy establishes a connection with the remote cache; in response to determining the resource is indicated as cacheable in the near cache, retrieving the resource from the near cache or from the remote cache when the resource is cached; calling an administration microservice to obtain the resource when the resource is not cached, wherein the administration microservice is a different microservice than the first microservice; and providing the resource to the client. - View Dependent Claims (14, 15, 16, 17, 18, 19)
-
-
20. A system comprising:
-
one or more processors; and a non-transitory computer readable medium having instructions stored thereon that, when executed by the processors, cause the processors to provide cloud-based identity and access management, the providing comprising; receiving a request from a client for a resource, the request comprising a call to a first Application Programming Interface (API) that identifies a first microservice, the resource comprising metadata; authenticating the request; accessing the first microservice of a plurality of microservices based on the request, the first microservice comprising a remote API proxy and a near cache, wherein the near cache is local to the first microservice and fronts a remote cache; determining, by the remote API proxy, whether the resource is indicated as cacheable based on the metadata, and if cacheable whether the resource is cached in the near cache or in the remote cache, wherein the remote cache is external of the first microservice and the remote API proxy establishes a connection with the remote cache; in response to determining the resource is indicated as cacheable in the near cache, retrieving the resource from the near cache or from the remote cache when the resource is cached; calling an administration microservice to obtain the resource when the resource is not cached, wherein the administration microservice is a different microservice than the first microservice; and providing the resource to the client.
-
Specification