DNS Hosting discovery: Caching

[abroddrick]

Issue description

We will be adding in the cloudflare Tenant api to use for setting and retrieving dns records. We will send the commands to "put" dns records in their system, while we will be saving these in our database it's imperative that we make sure to routinely do a get (or read) call to retreive what cloudflare has stored and update our system if there is ever a discrepancy. That said, when doing these get calls we should look at caching the response for a short time, as caching on “gets” to a third party api is common practice, especially when things shouldn’t be constantly changing. Caching should always be reset when we do a command that we know may change data (ie create, update, delete). The main questions for this investigation is how to cache and how long to hold onto the cache.

Assume for now that the cache will be added on get calls, you do not need to further investigate what gets cached.

Acceptance criteria

• read, update and add to the current options for caching as is applicable (feel free to add another option if one jumps out at you)
• Update the architecture impacts section indicating the choice made from the options (see additional details)
• determine which option to go with and get feedback from other engineers to evaluate your decision
• update the decision log with your decision

Additional context

For updating the architecture impacts, it can be as simple as writing "on all get calls we should add XYZ and then on all calls setting data we should clear the cache by doing abc". Feel free to include code snippets from docs as needed.

Links to other issues

• relates to Investigate Cloudflare CRUD commands #2874