As a web architect

Based on your work experience, let's talk about your opinion. as a Web 2.0 website architect, some basic knowledge and capabilities are required. Since they are personal opinions, it is inevitable that they are biased. my personal work on web is actually very short. I summarized the problems I encountered at work.

First, let's talk about the requirements for a Web architect's capabilities:

System planning capability (supporting the overall framework of the system, logical distribution of the system, physical deployment, and scalability)

Product planning capability (Web 2.0 is essentially a web-based business application)

If you do not really understand your business, your core needs, or typical behavior of your target customers, it is difficult to do a good job on your website. From this perspective, a Web architect must first be an outstanding product manager. Most of the time, we only need to lead the business technology, and blindly pursuing the advanced technology will be stuck in the quagmire. The simpler the clearer the problem, the better the problem can be solved.

Finding a balance between technology and business means that you must understand the core competitiveness of the entire business? What are the basic demands of the target group? Then select the lowest-cost technology to meet business needs, but in turn, you must reserve the appropriate platform space for business development. Technology exists because of the business reality.

Good user experience/Better interaction design

No matter what technology is used to provide a good user experience for real interface operations, at least the habits of users, users' operation hobbies, and good functional navigation require an overall planning. As for what technology is used for reality, it is a technical problem.

At the technical implementation level, we should make a good plan at the early stage of system development. For example, for common user prompts and function prompts, Ajax is used to implement a new technology without any need.ProgramThere are many methods, but which one is used? There is always a need for a plan, so programmers cannot play it themselves. In the end, all the corners are full. It is not easy to control, and the time spent on debugging JS + CSS is later than the debugging backgroundCodeThere is a lot of time. If there is a clear plan and specification that allows programmers to implement it, the problem will become more controllable in the future.

RequiredDefine effective specifications and implementations.

The goal of defining these interaction technologies is to achieve the best interaction in the simplest way, which is the responsibility of the architecture. Interactive Processing framework (including implementation technology and call specifications)

Reasonable storage design

One of the biggest features of Web2.0 is the massive storage of user information and the processing of interactive information. There must be a good design and expansion plan for storage,

The performance requirements for data storage during concurrent user operations are obvious, which may result in poor performance of the entire website. Therefore, you must ensure the scalability of the storage. Otherwise, however, user data cannot be split due to bottlenecks ...., but more importantly, it cannot be over-designed, and over-designed will become a disaster.

In the startup phase, a simple and direct relational database can be used. You don't need to spend too much energy to think about it. You just need to roughly test the capacity of a server, then we can estimate the amount of time you have to spend to reach the upper limit of capacity. That's enough. To put it simply, a file server and a database server do not make stupid mistakes. For example, a file has only one directory and cannot be split. For example, a database has only one table, too many logic coupling and so on. Since there is no, let's do it. As the business grows to a certain scale, if there are already 0.1 million users, it is no longer possible to ignore your storage. At this time, we will find that, many performance problems are caused by unreasonable storage problems. In this case, the storage design should be considered for performance. With the development of a larger scale, the manageability and cost of storage are gradually becoming the key. For architects, it is particularly important to select different design strategies in different periods.