3 ms·
I work at Bleacher Report. We use caching. Everywhere. As much as possible. We can probably do more. Just because we end up using that cached content to create
by abritinthebay 11y ago
I work at Bleacher Report. We use caching. Everywhere. As much as possible. We can probably do more.
Just because we end up using that cached content to create a unique mix for each user doesn't mean that we don't cache. I think you misunderstand the process.
- rubiquity 11y agoI stand corrected. This conference talk had me believe otherwise: https://www.youtube.com/watch?v=xT8vDHIvurs https://www.youtube.com/watch?v=xT8vDHIvurs
- abritinthebay 11y agoMichael's great, one of the smartest engineers I've worked with, but I don't think even he would say he meant to imply we don't use any caching at all. He's also mostly talking about our Elixir stack which is not our primary stack (though... we're hiring!). So it's a little bit of an edge case. There IS less caching involved in our Elixir stack though - due to how it functions - so maybe that's where the confusion arose.