Stack Exchange as one example aggressively uses Redis as a caching layer for practically its entire service. Redis is very fast, dependable and relatively easy

Stack Exchange as one example aggressively uses Redis as a caching layer for practically its entire service. Redis is very fast, dependable and relatively easy to use. The alternative, other than a competing product, is pretty much that you have to write your own custom replacement Redis in some manner. That might be fine at a small scale for fun or in an experimental product that isn't meant to go into production; otherwise you want something well proven, that many other engineers you can hire are likely to have experience with (it's hard to over-emphasize that last point). https://meta.stackexchange.com/questions/69164/does-stack-exchange-use-caching-and-if-so-how/69172 https://meta.stackexchange.com/questions/69164/does-stack-ex...