Redis uses watch to complete the second kill snapping function

Redis uses watch to complete the second kill snapping feature:

Using two keys in Redis to complete the seconds Kill snapping feature, Mywatchkey is used to store snapped up quantities and mywatchlist user store snapping lists.

It has the following advantages:

1. First select the memory database to snap the speed extremely fast.

2. Fast concurrency is not a problem, naturally.

3. Using pessimistic locks can quickly increase system resources.

4. More than the team powers, the queue will make your memory database resources instantly bursting.

5. Use optimistic lock to achieve comprehensive requirements.

I think the following code is definitely what you want.

[PHP]View PlainCopyprint?

2. <?php
4. Header ("Content-type:text/html;charset=utf-8");
6. $redis = new Redis ();
8. $result = $redis->connect (' 10.10.10.119 ', 6379);
10. $mywatchkey = $redis->get ("Mywatchkey");
12. $rob _total = 100; //Number of snapped up
14. if ($mywatchkey <$rob _total) {
16. $redis->watch ("Mywatchkey");
18. $redis->multi ();
22. //Set delay for easy test effect.
24. Sleep (5);
26. //Insert snapping data
28. $redis->hset ("Mywatchlist","User_id_". Mt_rand (1, 9999), Time ());
30. $redis->set ("Mywatchkey",$mywatchkey + 1);
32. $rob _result = $redis, exec ();
34. if ($rob _result) {
36. $mywatchlist = $redis->hgetall ("mywatchlist");
38. echo "snapped up success!  <br/> ";
40. echo "remaining quantity:". ( $rob _total-$mywatchkey-1).  "<br/>";
42. echo "user list:<pre>";
44. Var_dump ($mywatchlist);
46. }else{
48. echo "Bad luck, then snapped!" ";  exit;
50. }
52. }
54. ?>

Redis uses watch to complete the second kill snapping function (GO)