Electricity supplier class - a high concurrency scenarios treatment

I simply said that under

Scene Description: spike scene

1. First, the total number of sync Redis by Redis decrementing, the request to stop receiving 0
2. The request came in on mq, to ​​consume
3. Consumer success Needless to say, post-consumer fails, the failure of the consumer user id or phone number into another in mq, mq buying failed to inform the user, in addition Redis then incremented by one, you can continue to receive a user request

OK