Give the confused Java staff some pertinent advice, or you'll be ruined.

A lot of people have recently asked me how to be a well-paid architect and one who is confused about the current state. I am here to make a simple explanation, or for the confused you have some help.

Do you feel confused at present?

There are a lot of people who are bored with the present job, because the current job is to achieve business, without any technical improvement. In this state will feel confused, especially the thought of the future of this feeling of confusion is even stronger.

Not so confused as to say is worried, with the passage of time, their technology has not improved, so feel worried.

There are two types of people:

* goof off, one day at

This kind of I will not be too much discussion, no meaning. I've also met a lot of these colleagues, and this kind of programmer has been wasted.

* Want to improve your technology, to the architect's direction.

Most of the people who send me private messages are this one. First of all, it can be seen that these people are people who have their own ideals, will also put into practice. Want to go to the architect direction, but have no one to take, and do not know how to become a framework division. If it doesn't change, such programmers may also be useless.

I would like to take this article and talk about the architect this topic, purely personal understanding, and right and wrong worry-free.

What is the architect's definition?

The individual feels that the architect needs to have the following characteristics:

Breadth of knowledge: need to know why mainstream technology is born, what can solve the problem? What are the pros and cons if the same business is implemented with unused technology? For example: What are the pros and cons of the popular ORM framework MyBatis and hibernate? A clear understanding will make the right decision when it comes to technical modelling.

Abstract Ability: Abstraction of business and technology. Business abstraction is the ability to create the perfect entity classes and their connections after analyzing the requirements. Technology abstraction is a layering of the overall architecture and interaction between the layers. This is critical if the technical abstraction is insufficient, which can lead to an inflexible architecture of the entire system, which is difficult to maintain and extend.

Depth of knowledge: at least in a field of experts, such as Message Queuing, ACTIVEMQ familiar with its source code, know its implementation.

Excellent learning Ability: learn new technologies and cutting-edge technologies and use them to solve business problems at work.

So how do you do it? I think you can start with the following steps:

1: Solid Java Foundation, Think in Java to understand the content described, to do this step congratulations to become a programmer.

2: Skilled use of mainstream framework, such as: Mybatis,spring.

3: Studied at least one web-based framework of source code, such as spring MVC, struts and so on.

4: Architecture over or participate in high concurrency system design, know how to deal with unexpected situations.

5: To their own business can be based on their own knowledge dimension, the proposed optimization or forecast its risk points.

In fact, can become an architect with the opportunity to have a great relationship, such as a programmer, the above has done, but the company did not give him the opportunity to do, a real framework of opportunity. Because before the architect does not leave, he will not have the opportunity, this is the reality!

Working 1-5 years of programmer friends face the current technology, feel very confused can add group 744677563, there is Ali Java senior Daniel Live to explain the knowledge points, share knowledge, the course content are teachers of many years work experience combing and summary, with everyone comprehensive, Scientific establishment of their own technical system and technical knowledge!

Give the confused Java staff some pertinent advice, or you'll be ruined.