Thanks Rob. 

I have implemented a function wrapper to change namespaces before an operation and then reset it again afterwards, and it seems to work reasonable well.  As we are intending to insulate customers' data from each other with namespace allocation, it does seem to make sense to have a battery of QEWD instances with one running for each namespace, as it will reinforce the separation of services between customers.  This will be a topic for discussion with the rest of my team.

Hi Rob,

My company is implementing a REST API for a browser-based client to interact with  our Cache database.  I found the example very useful, and I am happily able to get data from the database and present it to the client in JSON format.

As we are looking at separating customer data by namespace, I wondered if it is possible dynamically to change the namespace that QEWD is connecting to, without having to restart my QEWD Node application with a different set of configuration options?