The decision to maintain Redis as our underlying cache type allowed us to swap from self-hosted cache nodes to a managed service nearly as simply as changing a configuration endpoint.
Here are some parameters and errors.
For example, some of our Redis nodes store processed data from multiple source-of-truth data stores, and we found that we could not easily configure DAX for this purpose.
Our sharding algorithm was inefficient and led to systematic issues with hot shards that often required developer intervention.
ObjectRocket offers on-premise offerings, which they hope will ease that transition if that day ever comes.