Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • Note that the assertion that Redis is “blazing fast” is a highly subjective opinion. For the scale of systems I am involved with the performance of Redis is woefully inadequate, so it just depends what you are building. Commented Aug 11, 2018 at 6:38
  • @bikeman868 of course. Although, I would say for the vast majority of webapps, that statement holds true. Redis is single threaded, so as things start to scale, you have to start changing things. Just curious, what solution are you using? Commented Aug 13, 2018 at 13:05
  • 1
    After battling with Redis etc for way too long, we eventually built an in-house equivalent that is more than 100x faster than Redis for our particular scenario. Commented Aug 13, 2018 at 15:52
  • @bikeman868 now im curious what your usecase is =) Any details you can give? Commented Aug 13, 2018 at 16:56
  • 1
    I used it to store session data for each user. We do not use sticky sessions so the session needs to be accessible and updatable from multiple servers. The session must expire after a configurable interval, and is deleted on logout. I also wanted to be able to serve multiple requests to the same user at the same time without locking the session. We have about 100M registered users and serve about 50K requests per second. Commented Aug 14, 2018 at 2:43