Apigee Cache Limits OPDK

In Apigee OPDK, we have a design need to store around 7 million active entries in Cache. I understand the OPDK limits of 2.3 million entries per cache and 100 caches per environment but indicated as planned.

Anyone issues/concerns/considerations if we are to store multiple caches to cater to 7 million entries?

Looking for help if anyone has done any such implementations and possible to share the the design patterns and considerations and issues encountered if any.

0 1 108
1 REPLY 1

Anyone issues/concerns/considerations if we are to store multiple caches to cater to 7 million entries?

What's the use case here? 

While it will come in under the limit, there are obvious concerns around DB size and lookup performance that come to mind.

 

Could you use custom oauth attributes instead?

https://docs.apigee.com/api-platform/reference/policies/oauthv2-policy?hl=en#attributesattribute