raulk(@raulvk):this is the kind of systems intuition I’m afraid we are losing - read/write-through caches tend to be optimizations, not authority - the system can work without them, just slower - we design systems to continue operating even when the cache goes offline (graceful degradation) - therefore, durability should be disabled from day 0, because: - when you recover, your snapshot would be stale anyway, so it’s unsafe to use it - hence it was useless to create it in the first place

2026.09.11 13:28

this is the kind of systems intuition I’m afraid we are losing - read/write-through caches tend to be optimizations, not authority - the system can work without them, just slower - we design systems to continue operating even when the cache goes offline (graceful degradation) - therefore, durability should be disabled from day 0, because: - when you recover, your snapshot would be stale anyway, so it’s unsafe to use it - hence it was useless to create it in the first place

Daniel Lockyer@DanielLockyer

2026.09.11 12:30

If you're running Redis as a simple cache, you should probably turn off snapshotting and journalling Data is lost after a restart, but you save on so much CPU usage