Does not work out of the box. After setup, the memcached interface can be accessed using telnet and the redis one using redis-cli (to a certain extent; setting/getting individual values work with individual invocations of redis-cli, but connecting with redis-cli in the command interpreter mode does not), but neither of them work with the storage implementations of the MaxScale cache. In the memcached case there is a timeout error and in the redis case, it responds with something unexpected.

One problem seems to be the binary keys that the MaxScale Cache uses. If those are converted to hex-strings, then one error disappeared. So, out of the box the MaxScale cache does not work with Momento, but with some tweaking it might. But in that case it might be better to simply write a new storage implementation for the native Momento API.