First, the difficulty is that the auction system to change the status of the auction: how to be in time to the beat of goods after the change in the film, shot at the end of commodity time expired, how successful or change the auction unsold and so on;
Second, the case involving timers and thread, followed in the case of a cluster deployment lock needs to consider the independence of the auction thread;
A simple question about the recording process of doing that appear:
Always let it figure out how to change state at the start of the thread: is the relationship between the state of the page changes and the use of threads, internal threads run state changes per second, it stands to reason that the page should be pushed to the back end of the page, but first Edition is a simple version of the brush can temporarily page timing, late improvements need to optimize this; there is a commodity to be shot at startup should be a separate timer starts, and then a separate thread to run, push the internal automatic time change;
Knowledge shortcomings halfway encountered are: bean problem can not be injected inside thread, automatically scan the entire project is used, so for their own classes to be injected have to manually obtain and inject; otherwise is to run does not make sense;
Temporarily record these, and all other post-optimization good to share in the code;