Support for AWS ElastiCache memcache (dynamic client mode)?
-
Amazon AWS provides ElastiCache, a hosted memcached solution. One of its major benefits is “Cache Node Auto Discovery”, where instead of configuring the list of memcache server hostnames and ports (which might change at any time when the cache cluster scales up or down, or a node dies and is replaced) you configure a “configuration endpoint”, and then the memcache client (at connect time) retrieves a list of cache servers.
Documentation on this can be found at https://docs.aws.amazon.com/AmazonElastiCache/latest/UserGuide/AutoDiscovery.html – the gist is that the “configuration endpoint” is a DNS record that contains CNAMEs for all of the cache cluster endpoints.
Amazon provides a PHP extension that supports this, but it seems to only be compatible with the “memcached” PECL extension, whereas w3tc seems to use the “memcache” extension.
Is there any likelihood of switching over to “memcache” to support this, or alternatively implementing ElastiCache dynamic configuration in w3tc (i.e. implementing a cluster client – amazon’s reference is OSS)? I’d be willing to try to submit a patch if there’s interest.
This is also a concern because with ElastiCache, if I want more memory (spin up a larger cache instance), the DNS name for the memcache instance will change. Since this is configured in an on-disk file, I would need to terminate the running WordPress instances in order to get the new address.
- The topic ‘Support for AWS ElastiCache memcache (dynamic client mode)?’ is closed to new replies.