Caching strategies for read-heavy APIs: when doest Redis beat Memcached?

hey everyone, ive been thinking a lot about caching recently, especially for our read-heavy internal APIs. we currently use Memcached, and its been solid, but im wondering about the trade-offs with Redis. specifically, im curious about scenarios where Redis's data structures (lists, sets, sorted sets, hashes) offer an advantage over Memcacheds simpler key-value store, even if the primary goal is just faster reads. are there specific access patterns or data types where the overhead of Redis is justified by the benefits? whats your experience in choosing between them for different caching needs?