title: Having a local and a remote client with Redis
body: <p>I want to set some write constraints in Redis and I was thinking to store these constraints in hashes. </p>
  
  <p>My initial idea was to modify the set commands so they check the rules before they write in Redis. I was thinking that by this way the check would be super fast. Of course such an approach would demand more modifications every time that Redis is changed, which I find a little bit hardcore if you think that it is about a school assignment. </p>
  
  <p>The second idea is that there are 2 types of Redis clients. One in the web application side (might be several instances of the web application) and one on the Redis machine. Based on this idea come my questions.</p>
  
  <ol>
  <li><p>Would the 2 clients (local and remote) have increased performance in comparisson to 1 client that first checks the constraints and then writes in Redis? Or should I stick to the one client that does it all (phpredis or predis, the application is on PHP, with some modifications for the constraints check)?</p></li>
  <li><p>If I could try the 2 clients, in which programming language would be better to be implemented the local client (C, Lua or other)?</p></li>
  </ol>