when does redis become more than just a cache

Right now, our main app database uses Redis mostly as a cache. It works okay, but I'm wondering when other folks started considering Redis for other things, such as rate limiting, storing user sessions, or even as a simple message broker. Are there particular signs or patterns that make these other uses seem better than just keeping it as a cache? Also, what should we watch out for when we give it more jobs?