3 ms·
I know that you're thinking: "Premature optimization is the root of all evil". But when I use caching, I don't consider it premature at all. It's just a best pr
by cellis 17y ago
I know that you're thinking: "Premature optimization is the root of all evil". But when I use caching, I don't consider it premature at all. It's just a best practice, like not writing O(n^2) loops. Why wait until your site starts to "bog under load"?
- jrockway 17y agoIs it easier to add the cache or not add the cache? If it's the second one and you do it anyway, it's premature optimization. Like the OP says, this may obscure other problems that you can fix with less effort. You want a simple system that is good, not a complex system that is "good enough". You can add complexity later, but it's very hard to remove. So be careful about that. If all of your sites follow some similar pattern, then you aren't doing the optimization, your framework is. And that's fine; presumably you already tested the framework and didn't introduce any unnecessary complexity.