search

KumologicaHQ / kumologica-support

3 stars 0 forks source link

Cache a request for 24 hours is all query parameters are the same #31

Open kensowens opened 2 years ago

kensowens commented 2 years ago

Hello,

Hope you are having a great day! I am trying to find a cache scope within Kumologica so if a user try's submitting the same request in a 24 hour period that they will not hit an http endpoint and instead hit a cached response. Thanks for your help. Please let me know if anything else is needed.

Thanks Kenny

sparkyrider commented 2 years ago

Non KumoTeam Response Here: Are you deploying to AWS or Azure/GCP? All of the platforms have caching support such as AWS's API Gateway, etc.

kensowens commented 2 years ago

I am deploying to aws

Thanks Kenny

On Wed, Oct 20, 2021, 09:59 sparkyrider @.***> wrote:

Non KumoTeam Response Here: Are you deploying to AWS or Azure/GCP? All of the platforms have caching support such as AWS's API Gateway, etc.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/KumologicaHQ/kumologica/issues/31#issuecomment-947856707, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI267R52X4FAQDZTIUGTKADUH3YNNANCNFSM5GKOAQSA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

sparkyrider commented 2 years ago
Screen Shot 2021-10-20 at 1 40 49 PM Screen Shot 2021-10-20 at 1 40 58 PM
sparkyrider commented 2 years ago

See the screenshots above. When deploying to AWS using the API Gateway, you can configure API cache settings. This may help you

kensowens commented 2 years ago

Thank you

On Wed, Oct 20, 2021, 11:42 sparkyrider @.***> wrote:

See the screenshots above. When deploying to AWS using the API Gateway, you can configure API cache settings. This may help you

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/KumologicaHQ/kumologica/issues/31#issuecomment-947938603, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI267R4AZLBHGYGEW6G6XBTUH4EQ7ANCNFSM5GKOAQSA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

ab73863 commented 2 years ago

@kensowens ,

As mentioned by @sparkyrider since you are deploying on to AWS , the caching option provided at API Gateway level would be ideal for your requirement.

If you are looking for caching within your service then there are multiple options that you could leverage and Kumologica supports nodes for the same.

eg : using DynamoDB as a caching and lookup service using AWS SSM store using Redis cache using AWS Elastic Cache