so, what about caching strategies for data that we access a lot, but doesn't change much
Umar Benali
·3695 views
Hey everyone, I'm working on a project with tons of data that gets read a lot but updated only now and then. Stuff like config settings, user preferences that don't change much, or even just static content. We want to figure out the best ways to cache this data to make things faster and take some pressure off the database. What do you usually do for caching in this situation? Do you use in-memory caches, something distributed like Redis, or another option? Also, any advice on how to handle cache invalidation when the data *does* change would be awesome.
36 comments