riFaulkner
commented
2 years ago Marking this as a p2, even in a day with pretty heavy development where I'm getting all contracts and their players for a league I'm still only getting to about 8k reads. I think until we start allowing users to look for players we'll be fine.
If we start to hit the overage this should be a pretty easy implementation and we can add it where needed.
To help prevent us from going over the 50k read threshold add some basic caching to resources that don't change very often. these can have a relatively short TTL of 30 min to 1 hour. Some resources that would be good candidates for caching; user preferences, player data.
Player data is particularly query intensive and would reduce the number of DB calls by a significant margin.