Implement Caching Layer #3
Description
Context
Any database would be getting a bit of a kicking during moments of high-traffic. I'd may want to introduce a memory provider (e.g. Redis) to cache consent checks. It would take the pressure off the disk and make the API much snappier when we are hammering it with thousands of requests, which may be the case when an external automation tool has sent out a campaign.
Alternatives
Scaling the DB vertically, but that is a bit of an unwanted fix compared to proper caching.
Has the feature been requested before?
No.
If the feature request is approved, would you be willing to submit a PR?
Yes.