Case Study – ElastiCache website overhaul – draft

The ElastiCache site had previously been split into two outputs, generated from the same set of base XML files. One site was ElastiCache using the engine Redis and the other was ElastiCache using the engine MemoryDB.

This split had seemed convenient at one point, but was now causing confusion for users and added difficulty in maintaining for AWS. Also, AWS had decided to create it’s own fork of Redis to be called Valkey, which would further add confusion as either an entirely new site or a sub-version of Redis.

My proposal was to reform the previous ElastiCache and MemoryDB sites back into one. And in the process simplify redundant pages and entirely eliminate unneeded internal complexity.

Result: immediate drop in NPP ratings, increased traffic, and most importantly happier customers.