title: Redis - very large single record (hash table)
body: <p>We have a huge dispute in here:</p>
  
  <p>We have Redis installed on the server and we want to save a few types of data in it:</p>
  
  <ol>
  <li>Some sporadic variables (for every user - so not just a few records)</li>
  <li>A very large table <strong>that will grow over time</strong></li>
  </ol>
  
  <p><strong>The dispute is how to save the mentioned table</strong></p>
  
  <p>We all know that Redis GET time complexity is O(1) - so we can store every record of the table as a record in Redis (with some prefix to know it's that table row)</p>
  
  <p>OR</p>
  
  <p>We can store the table as a single record inside Redis as a hash - and then access the row we want inside the hash - that's two O(1) steps.</p>
  
  <p>I think that a huge ever growing SINGLE record inside Redis is catastrophic, but I need more than my opinion about it - I need a Redis expert response that will point the finger at the faults in that method or will prove me wrong.</p>