29 ms·
abc - always be caching. Seriously if it’s in the db use an index - it’s a cache. If you can’t get an index - background worker into a cache
by taf2 5y ago
abc - always be caching.
Seriously if it’s in the db use an index - it’s a cache.
If you can’t get an index - background worker into a cache
- Gigachad 5y agoCaching is a significant source of bugs and complexity. Often really bad bugs too, like serving one users data to another user. Only be caching when there is a decent performance gain to be had.
- forgingahead 5y agoI think the author had some good points about when to use caching - it's unlikely for the vast majority of readers on this forum who would need a speed up benefit from 10ms to 5ms just because of caching, precisely because of the complexity cache management involves. There's that old joke: What are the two hardest things in computer science? Cache expiry, and naming things.