Crypt & cache remote. Which one should be on top of which one?

Hi all,
I'm confusing on what's the difference between creating a crypt remote on top of cache remote VS cache remote on top of crypt remote? Any performance impact & difference?

Check out right here:

In theory you can run either config, and the difference would be if your cache was encrypted or not.
It's easier to tinker with unencrypted obviously, but encrypted would be safer in terms of local security.

In practice it seems like some backends do not like the Cloud -> crypt -> cache setup so much and can react badly to it. I have never tested this against the general recommendation (and this could have changed since back then when documentation was written), but as the docs state the prefered method is Cloud -> cache -> crypt (resulting in a crypted cache, which I find preferable anyway outside of pure testing).

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.