Free Encyclopedia of Ecommerce :: Free Encyclopedia of Ecommerce

Scalability

Most average computer users have worked with word processing software applications that allowed them to select lines or blocks of text and increase or decrease the text's type size. This action is a very basic example of scalability, whereby the size of something can be changed (increased or decreased) according to need. In the case of e-commerce, the term scalability usually corresponds to the hardware, software, and network infrastructures used to keep Web sites and related systems up and running. Having scalable systems and applications is important for companies because it means that valuable resources and investments won't be lost when it is necessary to make changes to them.

From a technological standpoint, scalability can involve very simple actions like adding memory to a PC or server (computers used to host Web sites), increasing the number of nodes on a computer network, or adding new or more sophisticated features to an e-commerce Web site. However, it often involves a company's entire e-commerce architecture, which consists of many different technology elements. During e-commerce, companies rely on databases to store and present information about products (including prices, sizes, colors, and options), customers (including names, addresses, preferences, and credit card numbers), content that appears on dynamic Web pages, and more. Servers are another important piece of the puzzle. Finally, networks of workstation computers for staff, connected by miles of cabling and network hardware components, also play central roles. In an ideal world, it would be possible for a company to add, replace, or take away different pieces from this constellation without negatively impacting the entire system.

Unfortunately, such is not always the case. When companies find themselves in a position to grow, there are often hurdles that must be overcome first. Among these hurdles are old "legacy" systems that are still very important to the company's operations, but which were not designed for e-commerce. Although there are ways to connect legacy systems to e-commerce software, high volumes of transactions can present problems. Rather than establishing individual patches for many legacy systems, one possible solution to a challenge like this would be to replicate essential data from all legacy systems involved in e-commerce and place it into a special database called a data warehouse, which is compatible with the Web and e-commerce. This warehouse could then be scaled more easily, depending on the company's needs.

Two keys to scalability are size and replication. For example, a software application can be divided into different smaller sections or tiers, each corresponding to a different function or area of e-commerce. One tier might be devoted to a program's user interface while another deals exclusively with the data being accessed. Computerworld explained that successful e-commerce applications keep these tiers separated and require little interaction between them. This allows each layer to be more easily modified without affecting other system areas. If necessary, more memory or processing power can be devoted to one level of an application, but not to others. Replication also is key. When companies create a component for one area of their e-commerce operation, such as programming instructions that deal with accepting special promotional discounts, a good strategy is to then re-use this code in other applications or areas of the site, rather than re-creating it from scratch every time.

Besides technology, human systems can also be rendered scalable. Because the e-commerce business environment is dynamic and unpredictable, it requires e-companies to respond quickly to factors like volatile stock market conditions, pressure from investors and customers, new technologies, and competitive forces. A workforce that is truly scalable is one where many employees work remotely, instead of in the same physical location. Armed with laptops and telecommunications capabilities, such a workforce is able to grow (or shrink) as needed with less regard for other factors. Unlike companies where everyone works at the same physical location, the size requirements of buildings cease to be an issue in this scenario.

Rather than investing heavily in their own e-commerce systems, many companies opted to out-source different functions in the early 2000s. Application service providers (ASPs) were an attractive option. These third parties provided software applications on their own equipment and then charged customers for using it. As part of the arrangement, they assumed the responsibilities and risks involved. This was a cost-effective option for companies that needed to increase or decrease in size very quickly. In this scenario, the ASP makes the hardware and software investments, and the company is able to pay only for what it uses. One trend was that e-commerce software packages began including many essential e-commerce components, such as application servers, Web servers, and middleware (which allows different systems to communicate with one another). Along with choosing ASPs, more companies also were turning to third parties for Web site hosting. Although this did not decrease the need for scalability, Jupiter Media Metrix found that many executives underestimated scalability's importance. By doing so, they increased their chances of future problems, as well as additional costs.

FURTHER READING:

Desal, Gautam; Eric Sanchez, and Joe Fenner. "App Servers Meet E-commerce." InformationWeek, February 26, 2001.

Kurnit, Scott. "Scalability: Are You Fast Enough?" Chief Executive, February 2001.

Saliba, Clare. "Report: E-Biz Neglects External Web Hosting Options." E-Commerce Times, August 15, 2001. Available from www.ecommercetimes.com.

SEE ALSO: Outsourcing

User Comments Add a comment…

Scenario Planning - How Scenario Planning Works, The History Of Scenario Planning, The Future Of Scenario Planning [next] [back] Sapient Corp