Take you as a Java architect (write schema, not schema)

http://geek.csdn.net/news/detail/239195

Many people do Java Development 2, 3 years later, will feel that they encounter bottlenecks. What will be nothing, how to change the dilemma, why many people wrote 7, 8 years or a code farmers, work too much passive because do not understand the underlying principle. The company's work rhythm and relatively fast, difficult to have the opportunity to learn the structure of the principle, and no one to teach, so this time, learning the structure of the principle of expansion of thinking, for their future career is particularly important.

The same company's two new, a new person on the point, learning things quickly, some people, learning things are slow, but also very painful, everywhere are new technologies. Why. Because that person understands the principle, all things have the law, grasps the rule to learn other thing principle to be interlinked, one touches will, does not understand the principle to be everywhere to hit the wall, the study is very slow also very tortured.

Many programmers will have a distressed, work for a long time, in the company blindly change and check, not get the technology to improve, without the underlying code, will only use the principle of ignorance. Too many coincidences, let me access to open source, through JEECG with a lot of friends, let me have to help others learn the idea of the underlying architecture.

Here to share an architect learning roadmap

1. Engineering topics

2. SOURCE Analysis Topics

3. High concurrent topics



4. High-availability Topics

5. Performance Optimization Topics