3 ms·
The issue with caches is they are easy to apply. You can easily drop a cache in any place you load a resource without significant code changes. I tend to thin
by cogman10 4y ago
The issue with caches is they are easy to apply. You can easily drop a cache in any place you load a resource without significant code changes.
I tend to think they are ok weapons of sometimes first resort (rarely changing resource with heavy system impact). But you'll definitely get better results simply by rethinking and rearchitecting stuff. (Did you really need to load the database just to lookup a single value?)
- hinkley 4y ago> You can easily drop a cache in any place you load a resource without significant code changes. Only when the cache is brand new. The problem with people with cache addiction is that they think they're free. So once they know a cache is there, they begin to lean on it, and lean on it. I've seen it with many different teams in a number of verticals. Sometimes while I'm there, sometimes before I arrived. It's the people not the company. This illusion that you can always turn it off later is dangerous. That's only true if you have an impeccable information architecture when you start. And if you have that, you've already done a lot of heavy lifting before caching becomes your only option.