I want some hard stuff. Do you think the e-commerce system (the programmers behind it) will let you succeed so easily?
Every year, many people complain that they can’t get the products in a second: they either finish the products in a second, or they load them crazily after clicking the payment page, and then the products are gone after loading. At this time some people will move some crooked brains – let the scalper rob, a bit of technical basis can also be self-sufficient, write a reptile to buy.
A goose! You can think of it, programmers can think of it.
So, today I give you a second kill system is how to prevent malicious brush requests or crawler requests. Interested friends, you can also directly to listen to my lecture “seckill system project class” free of charge, understand the implementation mechanism of seckill system.
Firstly, in order to prevent malicious brush request or crawler request, the system will adopt the verification code mechanism.
But the captcha mechanism, which is very easy to crack, has been upgraded to 2.0: the answer mechanism.
The answer mechanism is harder for the machine to read (even I get some questions wrong).
Some small partners will find their account is “hacked”, can not enter a page, or constantly display operations, that is most likely to be limited by the platform’s flow limiting mechanism.
Generally, the operation method is to control the access times of the same IP address or control the same user ID. Whether the request comes from the same IP address or the same user ID, it will be judged as malicious request by the system and prohibit buying.
The most serious case is that the system will be blocked user ID or directly blocked IP address, into the blacklist. In this case, it’s approximately equal to —
Harm, so you are dou but programmer, or honestly squat point grab goods……
Let’s talk a little bit more about seckilling.
The second kill system is not only to prevent malicious requests or crawlers, but also has many important aspects to maintain. For example, the seckill system needs to face the scene of instantaneous high concurrency and large traffic, prevent oversold, require high performance and stable system, limit the number of items purchased by users, etc., all of which test the system architecture ability and coding skills of programmers.
Therefore, many technical points involved in the second kill system project are the key points of the interview for the first and second tier large factories, and also the technical threshold must be mastered in the large factory work.
In addition, about the second kill system related knowledge points
- Construction method of project environment
- Kill page and activity function development
- Distributed lock knowledge and code implementation
- Distributed ID solution
- Data consistency processing for payment and slowing down storage
- Current limiting principle
I said very clearly in the “second kill system project class”, now also open the first class free audition, interested partners may wish to experience.