We're making HTTPS calls from Node.js that require use of a client certificate. The certificate/key & associated password are read in from file and this all works. My concern though is having to read in the files for every request and the question is what is the best way to cache this.
Would using the apigee-access module to access the Edge distributed cache be the appropriate thing to do in these circumstances? Or would it be better to use one of the Node file caches that are available?
Solved! Go to Solution.
When i did a similar implementation - i just loaded my cert during initialization, and not in the request handler. So the request handlers need not load the files everytime. But the downside to that is, it is permanently loaded.