Small-scale low-performance low-traffic website design and development Principles _php Tutorial

Small-scale low-performance low-traffic website design and development principles

Often on some technical sites to see the analysis of large-scale, high-traffic, high-performance, such as the site architecture design articles, such articles are basically to meet people's curiosity, but after watching the actual income may not be large. Because most people may not have much access to this opportunity. Even when exposed, the actual situation is often different from many of the articles seen.

In addition, this article to see more of a side effect is easy to make people excited, did not learn to run first, so there are many people in many conditions still do not have the situation, excessive design, excessive expansion, premature to consider some unnecessary problems, the results often lead to backfire.

Today's article focuses on how small, low-performance, low-traffic sites should be designed and developed.

If the site start stage may be a machine or a space (such as www.phpernote.com this day IP is not over 5000 of the site), this time, we pay attention to what data splitting ah, load balancing ah, are no shadow of things. Many large site experience can not be copied, according to the actual situation dialectical view of the problem is the hard truth.

Embracing the familiar technology

Build a site, do not go around to ask others what to use, what familiar with what, if you do not good at the technical means to write the site, and so you finish, the flowers may be cold. So, with ready-made software components available, don't reinvent the wheel on your own. They say Python cows, but they only know PHP, then PHP good, if only familiar with. NET, that's good. Using rotten technology is not a shameful thing, the good technology with rotten to shame.

Clarity of the architecture hierarchy

The starting stage should clearly determine the level of the architecture. If all is mixed together, once the business expands, it is very painful if the original pile of things cannot be opened.

Web Server <--> (AppServer) <-->cache (eg. Memcached) <-->db

A manifestation of the clarity of the hierarchy is (take the LAMP architecture as an example): Even if there is only one machine, it should be a Memcached example, the effect is very good indeed. General I don't tell him, do not put everything on the DB, db all I/O pressure to go to the disk, the problem to be exposed is very fast. Yes, the DB itself uses its own cache, but the DB cache and Memcached design starting point are different.

How to treat data redundancy correctly

Many people are not database design experts, if a project needs to design a table structure or something, basically is cramming, but three paradigms many people remember very well, this is a headache for most small Web sites, a small project to engage in dozens of tables. Forget the paradigm, this thing!

Remember, as much as possible redundant data, now disk space price is not expensive, time is always more expensive than space. The more time you get stuck in the data layer, the less you will invest in the product. Users are more concerned about the design of the product.

Front-end optimization is important

Because the traffic is low, visitors may not be many, this time it is worth noting that the page is not too big, most of the low-traffic site loss is a page at a few megabytes (I saw a startup two days ago the home page has 4 m of the big, is amazing), the user to read a half a minute can not open, you say how development First, the basic conditions to meet, and then to study the front-end optimization.

Be cautious in adding functionality

Isn't there a 80/20 rule? Put the most important energy in the place that will bring you the most business value. Some fancy features bring a lot of overhead, but they have little effect. Remember, small sites, the most valuable is the business model, not your technology has more bull. Technology is for the business services, do not dazzle skills.

Some websites keep adding functionality, just to turn these new features into a straw to crush their own.

Consider performance from the start

This is optional, but also important. When designing an application, you should consider the profile at the beginning. Whether a set of applications can be effectively optimized and extended at a later stage is largely limited to the existence of a more appropriate profile mechanism. It should be added that the consideration of performance must take into account the relevant historical data.

A good architecture is not designed.

This is the last point to add. A good architecture has something to do with the original design, but the most important is the evolving evolution:

Development--Find problems--feedback--Problem solving (execution Force)--evolution to the next stage--new problem emergence (loop)

Some sites to a certain stage stop, may be stuck in the execution of this place, from the user feedback came up, there is no driving force to do the improvement. The last is lose. The most afraid of hearing is "business does not allow" the alibi, imagine if not improve the business is gone, the business also allow it? is actually a layer of psychological barriers.

This article has a strong cottage style, so you should not take it too seriously. If you are in a short, flat, fast way to build some of the cottage site, you can refer to the points which are good for you, unfavorable places can be ignored directly, there is no need to bother to argue the message.

Articles you may be interested in

• Compress website js and CSS files using PHP's gzip compression to speed up website access
• A good User Experience site home page design must know 12 points
• How to optimize server, static, database optimization, load balancing to achieve high load for large traffic website
• How PHP can turn on compressed output to website to enhance website access speed
• MySQL index Operations Command (CREATE INDEX, rebuild index, query index, delete index) summary
• The principle of exchanging friend chain with PHP Programmer's note-taking website
• PHP inventors Talk about MVC and web design architecture
• Google Blog Search enable ping to achieve real-time site content ingest

http://www.bkjia.com/PHPjc/889243.html www.bkjia.com true http://www.bkjia.com/PHPjc/889243.html techarticle Small-scale low-performance low-traffic website design and development principles often on some technical sites to see the analysis of large-scale, high-traffic, high-performance, such as the site architecture design of the article, this kind of article base ...

