"Large Web site technology architecture-core Principles and security analysis" reading notes

The value of the evolution of large web site architectures

the value of the site is that it can provide users with what value, is what the site can do, but not how it is done, so in the site is still very small to pursue the structure of the site is trifles, outweigh the benefits. Small sites need to do is to provide users with good services to create value, to get the user's recognition, live, savage growth.

Website Architecture Design Misunderstanding

Pursue the solution of big company blindly

The experience and success of large companies is important, it is worth learning from, but if it becomes blindly, it loses the courage to adhere to the ego, in the evolution of the structure of the road will be lost sooner or later.

For technical and technical

Website technology exists for the business, except that it is meaningless. In the technology selection and architecture design, away from the reality of the development of the website business, blindly pursuing fashionable technology, may introduce the development of Web site technology into the rugged path, the road of architecture is more and more difficult.

Trying to solve all the problems with technology

12306 The real problem lies not in its technical architecture, but in its business architecture.
Technology is used to solve business problems, and business problems can be solved by means of business.

Large Web site architecture mode

Website performance Optimization The first law: prioritize using caching to optimize performance.

Products at the beginning of the design needs a clear positioning: what is the product to achieve the function, what is not the characteristics of the product provided. In the product long life cycle, there will be a variety of difficulties and temptations to change the direction of product development, sway around, what all want to do products, and finally may become a lost vitality of the Sibuxiang.

The greatest value of a software architect is not in mastering much advanced technology, but in having the ability to cut a large system into N low-coupling sub-modules that contain a horizontal business module and a vertical base technology module. This ability is partly derived from professional skills and experience, and partly from the architect's understanding of the business scenario, the mastery of humanity, and even the perception of the world.

Scalable architecture for Web sites

Extensible architecture for Web sites

If you have a scalable website architecture, you can develop new products faster, perhaps you will not enjoy the benefits of only half class, but at least in this whole industry overtime in the Internet field, you can work on time, accompany family, look at the stars.

Architect Testimonials

Do not delay, learn something new, let yourself learn new things better. Keep your eyes wide open, and you may see the future coming to you. When it shows up in front of you, you'll find it's no big deal.

Use the right product in the right scenario, rather than the best product, the so-called feet wear big shoes, not only running fast, but also may wrestle.

Some road, after passing, then back, the list of the mountains small!

40 perplexed. That is, everything must be solved by itself, you do not have the qualifications and embarrassed to consult others.


The architect's leadership art

Focus on people, not products

Must believe: A group of excellent people do a thing they love, will be able to achieve success, no matter how tortuous the process, no matter how strange outsiders seem to be.
It is the things that make people, not what they accomplish.

Participate in the architecture together

Don't have an architect alone.
Let others maintain the framework and schema documentation.

Learn to compromise

Don't try to prove yourself right in the project, be sure to remember that you are here to do the software, not to be the boss. So don't try to prove yourself great, never do anything that wastes time and hurts feelings.
Often, objections to architecture and technical solutions mean that the architecture and technical solutions are focused, tried to understand, and accepted.
When you no longer discuss the architecture, it shows that the architecture has been integrated into the project, system, and developer, the sooner the architect is forgotten by the project team, the more successful the architecture is, the more the project team cannot be separated from the architect, the more the architecture has many drawbacks.