I'm a bit confused here, because the original comment was that "most people will never really see the point of Redis, which is that if it is running on the same machine as the application, it can respond in much less than a millisecond", to which the response was "there's more to redis than just being a K/V store".
I do see the point of Redis if you have multiple hosts, but I was unsure why someone would use it on just one host.
Right, it's still useful as shared data for multiple processes on the same machine. A SQL database mostly forces your data into one structure: the table. Redis instead provides commands which operate directly on those different data structures I mentioned.
I do see the point of Redis if you have multiple hosts, but I was unsure why someone would use it on just one host.