Caching subscription data

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

In describing the "read-mostly pattern" in gitlab-com/www-gitlab-com!78560 (merged), noticed that the information from the gitlab_subscriptions table may also be a good candidate for this pattern.

I haven't yet looked into this more, so this needs more investigation. The question is if we can cache a good part of the subscription data better - seeing that we very rarely write and quite often read this.