topics that matter; ideas worth sharing

share a tip, submit a link, add something new

Top 10 recommendations on building scalable, high-performance Web sites

February 13, 2001, 11:36 AM —  InfoWorld — 

A FEW WEEKS AGO, I wrote a column about eToys that generated a large reader response (see "eToys may not survive, but valuable lessons can be learned from its mistakes," Dec. 25 / Jan. 1). Most people chimed in to lament the hardships of the company. Several of you pointed out that I failed to mention one key factor in the apparent demise of eToys: its lawsuit against Internet art site etoy.com. Apparently eToys' actions ticked off a lot of netizens and resulted in a fairly significant boycott of the toy retailer. How much of an impact did the boycott have? It is impossible to know, although the bad will certainly didn't help.

Bad will isn't the only problem vexing e-tailers. Some of them can't seem to keep their sites running, which costs them big in terms of dollars and public face. At our U.S. Symposium last October, we at Gartner invited some clients to speak in a panel discussion about building scalable, high-performance Web sites. Here are the top 10 recommendations from those panel experts, in increasing order of importance.

10. If legacy systems work, don't replace them. As a general rule, spend time and money on new functions, not on old ones.

9. Build multiple Web sites. For example, Charles Schwab has multiple sites for its different lines of business, such as retail brokerage, institutional brokerage, and retirement services. Another company on the panel uses multiple sites to balance the needs of registered users vs. unregistered, occasional visitors.

8. Invest in proactive capacity planning and change simulation tools. Because user volumes can't be predicted, maintaining excess capacity is key. Charles Schwab maintains capacity at three to five times peak volumes, whereas AskMe, another panelist, assumes that 60 percent of peak daily traffic occurs in a four-hour period. Furthermore, the panelists strongly recommended using site performance simulation tools to understand the impact of increased user volume and changes to the site.

7. Invest in real-time availability and performance management. Monitoring real-time site availability and response time as well as component availability and performance statistics is vital to understanding site behavior.

6. Provide the appearance of 24/7 availability. Sometimes planned downtime can't be avoided. But designing the Web site to enable planned downtime for a portion of functions while the balance are available to users minimizes the overall impact of an outage. As a result, users have access to the site around-the-clock but may infrequently be denied access to some functions.

5. Invest in business continuity planning. Don't wait until a problem occurs to decide on a course of action. Instead, plan ahead for unforeseen events that could interrupt site access or degrade performance.

4. Design the site for no single point of failure. Designing the application architecture and technology infrastructure with redundancy minimizes the impact of component failures and resulting unplanned site downtime. Architectures should be n-tier, with redundancy in each tier from both a hardware and a software perspective. In addition, the physical datacenter should be designed for availability to reduce the impact of physical infrastructure outages due to maintenance or failures.

3. Dessign the entire architecture for horizontal scalability. By partitioning Web site functionality into components that live on different systems, enterprises achieve higher levels of availability and "pluggable" scalability. The design goal is to be able to add more capacity by deploying another server and load balancing a portion of the connections to it.

2. Don't ignore people and process issues. Good design does not eliminate downtime, because on average approximately 80 percent of site availability problems are caused by people and process issues, not by technology failures. So, to mitigate downtime risks, become adept at hiring and training.

1. Clearly articulate business priorities. Employees must understand business priorities (such as "the customer is always right"). Breed a culture that encourages teamwork, effective leadership, and solid communication. Furthermore, panelists recommended instilling fun and camaraderie into the culture to keep employees focused on goals.

» posted by ITworld staff

InfoWorld

I like it!
Post a comment
The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.
Resources
White Paper

Symantec Backup Exec 12 and Backup Exec System Recovery 8 deliver industry leading Windows data protection and system recovery. Download this whitepaper to find out the top reasons to upgrade and how to get continuous data protection and complete system recovery.

Webcast

Data and system loss — from a hard drive failure, malicious attack, natural disaster, or simple human error — can happen anytime. Don’t leave your business vulnerable. Make sure you have a secure recovery strategy in place. Symantec's latest backup and system recovery technology can efficiently restore critical applications, individual emails and documents and even restore your entire system in minutes in the event of a loss.

White Paper

Businesses face a growing challenge to ensure that the IT environment is properly protected. Backup Exec 12 integrates with other applications in the Symantec family of products, to complement your current data protection strategy, keep your data securely backed up and make it recoverable when you need it most.

Free stuff
Featured Sponsor

AISO founders envisioned a Web hosting company that was environmentally friendly. While the company employed energy-efficient innovations like solar panels, its infrastructure produced unacceptable power and cooling requirements. Find out how AISO leveraged AMD technology to overcome their challenge in this case study white paper.

In this whitepaper, Scalar explores the opportunity to change the landscape with respect to mission critical databases built around Oracle. Leveraging technologies such as Linux, high-end commodity processing power and Oracle RAC technology to architect, design, build and maintain database infrastructure that delivers maximum availability, reliability and performance at a fraction of traditional cost.

On a typical day, weather.com, the Web site for The Weather Channel in Atlanta, serves up between 15 million and 20 million page views. But in September 2004, when back-to-back hurricanes ransacked Florida, the peak traffic on one day more than tripled: over 70 million page views by more than 7 million unique visitors. Read the full success story now.

More Resources