设计基于Web的可扩展应用程序的关键因素

Question

Currently I am working on web based application. I want to know what are the key factors a designer should take care while designing scalable web based application ?

Answer 1

That's a fairly vague and broad question and something you could write books about. How far do you take it? At some point the performance of SQL JOINs breaks down and you have to implement some sharding/partitioning strategy. Is that the level you mean?

General principles are:

• Cache and version all static content (images, CSS, Javascript);
• Put such content on another domain to stop needless cookie traffic;
• GZip/deflate everything;
• Only execute required Javascript;
• Never do with Javascript what you can do on the serverside (eg style table rows with CSS rather than using fancy jQuery odd/even tricks, which can be a real time killer);
• Keep external HTTP requests to a minimum. That means very few CSS, Javascript and image files. That may mean implementing some form of CSS spriting and/or combining CSS or JS files;
• Use serverside caching where necessary but only after you find there's a problem. Memory is an expensive but often effective tradeoff for more performance;
• Test and tune all database queries;
• Minimize redirects.

Answer 2

Having a good read of highscalability.com should give you some ideas. I highly recommend the Amazon articles.

Answer 3

Every application is different. You'll have to profile your application to see where you should concentrate your optimization efforts. Some web applications might require database access optimizations, while others have complicated business logic that cause the bottleneck.

Don't attempt to optimize random arbitrary parts of you application without first profiling. You might end up having to support complicated optimized code that doesn't actually make your application snappier.

Answer 4

I get the sense from the other answers here that there is a general confusion between scalability and performance. High performance means that the response is quick. High scalability means that you get a response no matter how many others are also using the site at the same time. There's a big difference.

In fact, you actually have to sacrifice a little performance just to get good scalability. A general pattern to scalability is distributed computing. Factoring functionality out into separate tiers of clustered servers (web, business rules, database) is the usual approach to scalability. That extra round trip will slow down page load a little bit.

Everyone always wants to focus on high scalability but also don't forget that, for software vendors who sell licenses to customers who self host the application, scaling down can be just as important as scaling up. An application that can run on a single server for ten users but can also be configured to run on a ten server web cluster, a three server middle tier, and a four server database cluster for 10,000 users would be a system well designed for scalability.

Answer 5

None. Just code the application using proper design techniques (separation of concerns, etc) and then when the application is done or nearly done, do your performance testing. You'll find the real bottlenecks then - they won't be what you might have guessed in the beginning. This is where your proper design from the beginning comes into play - it makes it easy to make changes to fix the bottlenecks.

Answer 6

Sometimes, a specific answer is more helpful than just generic tips.

If you want to scale, the only thing to target is SPEED (in hardware and software) and RESOURCES (in hardware).

Hardware, the latter is expensive (more servers, load-balancers, etc.).

So, by carefully selecting your initial development framework you will save a lot of time and resources -up to several orders of magnitude.

For example, nginx is (much) faster than Apache.

Other solutions are faster than nginx (for both static and dynamic contents) but I could not disclose them without being censored on StackOverflow (it was rated SPAM & advertising despite the fact that this is a FREE solution).

That's the limits of "sharing": we must share only "acceptable" solutions rather than efficient solutions.

Cheers,

Pierre.