Feature Request: Client-Side Caching

[gruselglatz]

It would be nice, if there is some function to activate some sort of Client-Side Caching, to reduce the possibility of a single-point of failure.

Think of some sort of localhost service which works with some script on the same host, which gets the api password out of our centralized SQL-Database. If the Network-link gets down for some reason, the script would stop working.

Some sort of local encrypted configurable cache would handle this request.

Thanks in advance.

[domodwyer]

Hi @gruselglatz

I'm out the country for a while, I'll look into it when I get back. I'm not sure if I want to go this route, as having both the key and the encrypted blob on the disk is kind of against the point of the system. Plus client-side caching of encrypted data wouldn't work with KMS.

I'll have a think.

Dom

[domodwyer]

Hi there.

I don't think I'm going to implement this - it breaks KMS support and involves writing the secrets to the box next to the key if you go without KMS. Neither are particularly great. If the network link goes down, then surely your application is going to stop also?

Sorry! Feel free to implement it if it's a requirement for your system, the library is very simple to use.

Dom