3 ms·

This same argument applies to storing your relational data in a server separate from the app server, doesn't it?

• nostrademons 15y ago
  The difference is that relational data is usually disk-based, I/O bound, and requires persistence but not necessarily fast access. There're a bunch of algorithms that are specialized for the access patterns of disks (who wants to implement their own B-trees and transaction logs, other than Google?), so it makes sense to use an off-the-shelf solution for them. Redis's main selling point is being an in memory datastore, which is great. But virtually every programming language has a rich selection of in-memory data structures in its standard library, along with the ability to write code and implement some more. What is it that Redis gives you over using these? Programmers are generally quite familiar with efficient algorithms for accessing memory - it tends to be taught in intro CS.
  • deleted 15y ago
    [deleted]
  • Detrus 15y ago
    You're depending on each language's data structure implementation there. Redis aims to be more efficient than those.