7Expand
Multitiered Architectures (Linktionary term)
Tags: architecture, exam, mult, tier on 2007-12-18 -All Annotations (0) -About
in list: ISLifecycle
more fromwww.linktionary.com
-
Multitiered architectures are software models (and hardware models, as discussed later) that extend the basic two-tiered client/server model to three tiers. In the basic two-tiered client/server model, the client requests services and the server provides services. There are software interfaces on the client and the server side that connect with one another to handle these interactions.
-
However, the two-tiered model has some drawbacks. Both clients and servers run a portion of the application logic, with the servers handling the loads of back-end data management. This requires that client software be installed, managed, and updated on a potentially large number of systems. The two-tier model tends to move large numbers of records across the network to clients that may not always be optimized to handle them. The model is not efficient in distributed wide area network environments like the Internet. For example, a Web client may be a hand-held system with limited memory and processing power. It cannot be relied on to handle front-end processing tasks.
-
QL became popular as a form of client/server middleware because it was efficient at selecting and moving just the records that were needed. In addition, it could run stored procedures directly at the database server, rather than moving data to the client and then running procedures on the client. The three-tiered model extends this approach by moving application logic (the equivalent of SQL stored procedures) to a middle server called the application server. This server performs processing for the client and other tasks as necessary.
-
- Presentation services tier Responsible for gathering information from the user, sending the user information to the business services for processing, receiving the results of the business services processing, and presenting those results to the user.
- Business services tier Responsible for receiving input from the presentation tier, interacting with the data services to perform the business operations that the application was designed to automate (for example, income tax preparation, order processing, and so on), and sending the processed results to the presentation tier.
- Data services tier Responsible for storage, retrieval, maintenance, and integrity of data.
-
The Web is a good example of where to apply the three-tier model. Application developers know little about the potential clients except that they have a near-universal interface: the Web browser. The middle tier accepts requests from clients, retrieves information from the back-end systems, processes the data, and forwards the results to the client. The client is relieved of a lot of work. Thin clients are a good fit in this model.
The middle tier may provide the following services:
-
- The code for the middle tier can exist on multiple application servers, all accepting requests from multiple users (via load-balancing switches) and all connecting with the back-end systems.
- Message queuing allows clients to interact asynchronously with the back-end servers. In other words, transactions don't need to follow a precisely timed flow. The client may need to wait for a message from the server.
- The middle-tier server can provide transaction monitoring, which tracks the order and events of an online exchange to ensure that everything is complete and handled correctly. If not, the transaction is backed out.
- Distributed object computing services in which application logic and/or data resides in objects that are made available through an ORB (object request broker). An ORB provides a sort of software bus through which objects on one system can make requests of objects on another system. See "Distributed Object Computing."
-
The thin client model represents another aspect of multitier architectures. A thin client is a Web browser device that relies on an external server to run its applications and store its data. It displays information and accepts keyboard inputs. Some systems have small drives to cache objects from Web sites. A typical thin client is the inexpensive Internet appliance you've seen pictured on kitchen counters with TV-like knobs for accessing the interface. Users store data on a server located at a service provider or an online service. Electronic mail is accessed through a Web browser interface on a remote e-mail server. In this model, the service provider is the middle tier. In fact, giant Internet data centers are emerging to support this model. In some cases, the data center caches so much information via content distribution techniques that users are likely to find what they need at the data center rather than out on the bigger Internet. The Internet data center could be referred to as "Internet in a building."
Notation: * = Private bookmark and comment|… = Clipping [?] | … = Public highlight [?]
