Home > Articles > Programming > Visual Basic

Software Issues 6: Application Architectures: Past, Present, and Future

What is a tier, anyway? What can we learn from games? In this article, software development expert Tyson Gill discusses various strategies for architecting applications.
The content in this article is a mix of original material and material adapted from Visual Basic 6: Error Coding and Layering (Prentice Hall, 2000, ISBN 0-13-017227-8) and the upcoming book Planning Smarter: Creating Blueprint-Quality Software Specifications (Prentice Hall, 2001).
Like this article? We recommend

Back in the "olden days," when relational databases first started gaining widespread use, we wrote standalone front-end applications. Although we didn't know it at the time, we were writing single-tier applications. What this term means is that all the code is in a single application, including the user interface logic, the business rules, and the database management.

As these applications gained in popularity, it became evident that they were too difficult to maintain. Large companies might have dozens or even hundreds of users running the applications. Every time a business rule changed, the program had to be modified, recompiled, and redistributed to all those people. At that time, that meant some pitiful slob walking around the building running installs, reconfiguring, and troubleshooting, while all the time the users' work was interrupted. It got to be intolerable.

To mitigate this problem, efforts shifted to two-tier applications. By expanding the capabilities of stored procedures in the database, business logic could be moved there. That meant that stored procedures could be stored and maintained in one place. If they needed to be changed, they could be modified without having to recompile and re-deploy new program versions.

This architecture helped, but soon proved too limited:

  • As systems started to support larger numbers of users and the complexity of stored procedures grew, the load on the database became a limiting factor.

  • SQL is not a programming language. As stored procedures were pushed to do procedural things normally handled by powerful programming languages, the stored procedures became difficult to write, difficult to debug, and difficult to maintain.

  • Portability became an issue. To move to a new database required that all the stored SQL code—perhaps the majority of the complex code in the application—had to be rewritten.

To deal with these issues, three-tier applications became the accepted standard. In a three-tier application, you basically backed away from putting all the business logic in stored procedures. Instead, you moved business logic in a programming environment such as Visual Basic, and deployed that code as middle-tier components, DLLs. These business objects could reside on the database server or on entirely separate servers. This architecture allowed the developers to distribute services and load on three separate machines. It provided the benefit of a thin front-end program, a dedicated database, and business code, written in a powerful language and maintainable in one place on the server side.

It would seem as though this strategy should have met our all our needs. However, as Internet front-end programs became more common, the number of potential users jumped once more. When that happened, even these three-tier architectures were not enough. The middle tier couldn't handle the load.

The solution was to move to n-Tier architectures. An n-Tier architecture is basically a three-tier architecture with n number of middle-tier servers. Those servers can reside at different locations. Now the workload can be distributed in various ways across those servers; for example, by business function. Also, fault tolerance can be increased by having redundant servers in the middle tier.

Of course, there is a lot more to the story, but that's the bare bones. Now we've extended it further by not only scaling out our middle tier, but also our database tier, as well as providing intelligent load balancing and other services.

So far, we've ignored the Internet, and the Internet cannot be ignored. It has had and continues to have profound impact on application architectures.

So let's look back to the influence of the Internet. One of the many reasons the Internet took off so rapidly was that browser-based applications further reduced the maintenance requirements of front-end programs, and also solved connectivity issues through the World Wide Web. By creating a front end that was browser-based rather than VB-based, there was no need to do any installation or configuration. Installation and configuration has always been a major headache, even for a thin VB client. Therefore, when you have potentially tens of thousands of users, the browser was the only solution.

For a while, it looked like VB applications would soon be extinct and every application would be browser-based in a very short time. Although browsers didn't offer the kind of power and flexibility that VB applications provide, the benefits far outweighed the limitations for most customers. Browser developers scrambled to add more capability, and the entire world basically accepted the limitations of browser-based applications as a temporary condition.

Some developers and some marketers still think that all applications today need to be browser-based. However, the technical landscape has continued to shift. One of the main motivations for browser-based applications was ease of deployment. However, in the last few years Windows has gotten better about installation and configuration. It's going to get better yet. Terminal Services and Citrix offer a very efficient alternative for some applications. Finally, Active Update programs have dramatically lowered the maintenance barriers. Communication across the Web is now becoming transparently simple for standalone applications.

One great example of using these alternate approaches to architect sophisticated Internet-enabled applications is online gaming. The game guys are always way out at the leading edge of the wave. Everquest is one example of such a game. It's a heavy-duty client/server application running across the Internet. In Everquest's 3D world, thousands of players interact in real time. This application has an extremely heavy front-end application, consisting of over half a gigabyte of data and code on the local machine alone. And all of the critical information is stored and processed on the server.

This game simply could not have been developed within a browser. There are more than 300,000 Everquest subscribers; every time they run the program, it's updated automatically over the Web. Modifications are made almost daily, and all 300,000 people routinely get updated. If the designers of Everquest can accomplish this level of maintainability and performance, virtually any intensive application can follow this same model.

This illustrates the reality that you needn't think only of browser-based applications when you think of the Internet. There are other viable options, including Terminal Services–based applications, running inside or outside of a browser; installed applications running across the Web; even Internet-installed and Internet-updated applications.

The reasons that got us thinking only about browser-based solutions have already gone away. In the near future, the Microsoft.Net platform will make it even easier to copy heavy applications to client machines over the Web—without having to perform installations—as well as facilitate Web connectivity.

Which Architecture Should You Choose Today?

Evaluate your application needs prior to deciding on an architecture. The first question to ask is whether the application needs to be Internet-enabled. If the answer is yes, ask whether it's a casual or intensive application. If it's casual, think about a browser-based solution. If it's intensive, consider a shipped or Web-deployed Internet-aware application or a Terminal Services solution.

The distinction between casual and intensive is important. It's not meant to suggest a value judgment, but rather usage patterns and expectations. Casual applications are used only occasionally; for example, Web commerce applications such as online booksellers or trading sites. Users don't use these applications intensively or as part of the job. They don't want these sites to download and install custom components on their systems, and likewise don't expect functionality beyond what's offered by the browser.

An intensive application is a business application with heavy requirements that is used by employees or clients regularly to perform more intensive operations. These may include data entry, analysis, and reporting. Clients expect sophisticated custom interfaces to help them perform tasks efficiently. Managers expect to provide tools that optimize the productivity of their workers, not necessarily to make the task feasible in a browser.

While Internet Explorer is powerful, for example, it's unlikely ever to offer the power and flexibility of a standalone application. It's tremendous for casual applications, but often requires developers and users to make significant compromises in the design of more intensive business applications. Therefore, why spend a lot of time and effort and realize marginal results trying to force intensive functionality into a browser? There are alternatives.

On the other hand, why incur the overhead of supporting installed applications when the user would rather not leave the convenience of the browser for casual operations? The browser is clearly the best choice for casual applications. Other techniques may be better for more intensive applications. Of course, there is a wide gray area within which the choice is not clear. Time to market and the likelihood of expanding requirements are two possible deciding factors.

When we think of hosted applications, we think of browser or terminal services–based applications. However, hosted applications can be designed using any of these architectures. Everquest is essentially a hosted application for subscribers, but it uses an entirely different model based on an Internet-enabled standalone application.

The bottom line is that there are lot of good choices for developing Internet-enabled applications. The range of options keeps growing rather than becoming more monolithic. Just when it looks like one approach will dominate, different technologies emerge to compete. The trick is picking the right technology for the right application at any given time.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020