Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possibilities on Optimizing Http Remote Request #847

Open
kesavan-m-19 opened this issue Jul 2, 2024 · 1 comment
Open

Possibilities on Optimizing Http Remote Request #847

kesavan-m-19 opened this issue Jul 2, 2024 · 1 comment
Labels

Comments

@kesavan-m-19
Copy link

Hi @AndrewTriesToCode ,

I am using below modules in FinBuckle,

  1. Strategy - Delegate Strategy - To get tenant identifier from the request URL
  2. Store - Http Remote Store - To get tenant details via API of an another service

While implementation I have noticed that for every incoming requests API call was initiated to get tenant details. But I am expecting as, once tenant details was retrieved it needs to be reused for upcoming requests, instead of initiating another API call for getting same tenant details.

Can you confirm,

  • Whether this scenario can be achieved using FinBuckle?
  • Do I need to implement custom logic to attain this provision

Please share your suggestion on this requirement. Thanks in advance.

@AndrewTriesToCode
Copy link
Sponsor Contributor

Hi, you can register a cache store before the httpremote store and it'll first check the cache, if it doesn't find it, then it will add check the http store. You can configure it with the events that when a hit is found on the http remote store that it be added to the cache store. See #673 for a good solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants