Home > Articles > Certification > CompTIA

  • Print
  • + Share This
This chapter is from the book

Examples of System Architecture

As we have suggested previously, different answers to different issues can result in very different system architectures. In this section, we look at four different architectures and discuss how they are constructed. The four architectures are a Web server with an order form, an approach to distributed transactions originally created at Open Market, a large-scale federated commerce system, and an approach to business-to-business commerce originally developed by the Open Buying on the Internet (OBI) Consortium. There are, of course, many other approaches to Internet commerce; we chose these to illustrate many of the points discussed in this chapter.

For analysis of architecture, we have found it convenient to consider four primary components of Internet commerce systems.

  1. Client

    The client is a computer system, typically a personal computer, connected to the Internet either directly, through an Internet service provider (ISP), or indirectly, through a corporate network. The buyer uses the client computer for browsing and purchasing.

  2. Merchant

    The merchant is the computer system or systems that contain the seller's electronic catalog and, in the case of online goods, products for over-the-Net fulfillment.

  3. Transaction system

    The transaction system is the computer system or systems that process a particular order and that are _responsible for payment, record keeping, and other business aspects of the transaction.

  4. Payment gateway

    The payment gateway is the computer system that routes payment instructions into existing financial networks such as for credit card authorization and settlement.

Various architectures use these four components in different ways. In some systems, some of these components are combined into a single computer system, whereas in others these four system components are implemented by separate computer systems.

Once the designers of a commerce system have selected a gross division of function, there are still many decisions to be made at lower levels of functionality. For example, the order aggregation function, which permits the assembly of individual items into a complete order, can be implemented as part of the merchant, the transaction system, or the client.

Web Server with Order Form

Building a Web server with catalog pages and an order form is one of the simplest ways to construct an Internet commerce system. This approach is typically called a merchant server. A diagram of a representative system is shown in Figure 6-1, and a logical _diagram of the structure of the merchant server is shown in Figure 6-2. Many of the technical details will become clearer as we discuss the technology in later chapters, but we will sketch the basic ideas here.

Figure 6-1FIGURE 6-1. Merchant Server: Physical View

Figure 6-2FIGURE 6-2. Merchant Server: Logical View

In this example, a single Web server provides both the catalog content and the order form. In other words, the merchant server and transaction server are combined into one system, and there is no explicit payment gateway. The catalog might consist of a set of Web pages describing items for sale, with embedded pictures, drawings, specifications, video or audio clips, and so on. The Web pages might be created as static pages using an HTML editor, or they might be created dynamically from a database of items and descriptive information. Next to each item is a button that the customer can click to buy the item or add it to a shopping cart for later checkout. When ready to buy the item (or items, if more than one is present in a shopping cart), the customer clicks a Checkout button that starts the payment part of the transaction.

Payment by credit card is by far the most common method used on the Internet today for consumer transactions (as we discuss in detail in Chapter 15). A simple order form might consist of a listing of the items being purchased and a set of fields for the customer to enter credit card payment information, including the card number, the expiration date, and the address for delivering the items, if they are physical goods. The form might also ask for the billing address, because some credit card systems use the billing address as part of the verification of the holder of the credit card.

It is possible, of course, that the Web server might use a different payment mechanism. In the simplest version of this model, the Web client has no special capabilities for commerce, so the commerce application does not require additional software for payment mechanisms. Credit cards, purchase orders, and other kinds of account-based payments may be used with such systems, thus taking advantage of the basic security capabilities common on the Web today.

This basic architecture may be appropriate and sufficient for some kinds of Internet commerce applications. Its primary virtue is its simplicity. On the other hand, it may be more difficult to expand it as the online business grows, or to incorporate new technologies and components as they become available.

Open Market Distributed Commerce Architecture

The core architectural idea of this architecture is to separate the management of content from the management of transactions through a technology called SecureLink. This idea permits multiple catalog servers to share the capacity of a single transaction engine and allows the content-oriented parts of the system to scale independently from the transaction-oriented parts of the system. Separation of these functions allows separate management of several system facilities—most notably, security. This approach also permits service organizations to provide transaction management services on an outsourced basis for other companies. Figure 6-3 shows the physical architecture of this approach, and Figure 6-4 shows how functionality is distributed across different elements of the system. In this architecture, the transaction server is separated from the merchant server, and there may or may not be a separate payment gateway depending on which payment methods are supported.

Figure 6-3FIGURE 6-3. Open Market Distributed Commerce Architecture: Physical View

Figure 6-4FIGURE 6-4. Open Market Distributed Commerce Architecture: Logical View

Federated Commerce System

A federated commerce system (FCS) is a system made up of servers operated by different organizations and tied into an overall, perhaps global, commerce system by Web services and a collection of service agreements. In this system, consumers are members of communities of interest, which provide authentication services and customer service points of presence. When a consumer buys something, the necessary payment and shipping information is routed from her home community to the seller. The seller may also use some of the federated services for payment and other functions. At the conclusion of the transaction, a record is posted to the consumer's online statement held by her home community. From the consumer's point of view, only the home system is responsible for keeping online information. The essential architecture of this system is shown in Figure 6-5.

Figure 6-5FIGURE 6-5. Federated Commerce System

The federated commerce system includes

  • Clearinghouse

    The FCS clearinghouse is responsible for tying the network together. It permits the seller to locate a buyer's home community and helps establish peer-to-peer connections among the various participants.

  • Customers

    Customers browse for information, make purchases, and request customer service.

  • Home communities

    Consumers join home communities on the basis of interests, services offered, or the degree of privacy protections offered.

  • Sellers

    Sellers include merchants, service providers, and publishers.

  • Payment provider

    The payment provider provides support for various payment mechanisms as a Web service. It uses a common interface, which helps make sellers more independent of the payment systems.

  • Logistics provider

    The logistics provider handles shipping, returns, and other services.

We will return to this example in an extended form in Chapter 21.

Business-to-Business Purchasing

A closely related problem is managing purchases between businesses using the In_ternet. One architecture for such systems was proposed by the Open Buying on the Internet (OBI) Consortium, which was formed in 1996 to develop standards in this area. The consortium is a group of buy-side organizations, sell-side organizations, payment organizations, and technology companies that is addressing the problem of business-to-business commerce on the Internet. The core idea of OBI is to split the functionality of the commerce system between buy-side activities and sell-side activities so that each organization manages those functions logically connected to it.

The OBI design is based on a model of business commerce shown in Figure 6-6. In this model, the logical breakdown of activities is to place the customer database, _requisitioner profiles, and approval processes on the buy side, and to place the catalog, order management, fulfillment, and payment activities on the sell side. This structure results in the architecture shown in Figure 6-7. The key idea in OBI relevant to our functional components is the splitting of the transaction server into its sell-side and buy-side parts.

Figure 6-6FIGURE 6-6. OBI Business-to-Business Purchasing Process

Figure 6-7FIGURE 6-7. OBI Architecture

In order to make this architecture work, two elements of interoperability are needed between the buy-side and sell-side components: requisitioner authentication and order handling.

  1. Requisitioner authentication

    Because the buy-side organization assumes the responsibility in the OBI model for managing the pool of requisitioners, the sell side must have a standardized means of authenticating prospective requisitioners as authorized by the buying organization. OBI uses public-key certificates for this purpose. When the requisitioner browses the supplier catalog, he presents a certificate signed by the buying organization to validate himself. This approach implies that at the time the trading relationship between the companies is set up, the supplier catalog must be configured to accept the certificates.

  2. Order handling

    In OBI, the requisitioner builds up an order by interacting with the supplier catalog. That order is then sent in a standardized format called the OBI order request from the sell-side OBI server to the buy side. Once it is there, any necessary approval processes proceed. After the order is finalized, it is returned to the sell side as an OBI order for fulfillment.

The real benefits of the OBI choice of placing functionality can be seen only when there are multiple buy-side companies trading with multiple sell-side companies. When this happens, the buy side is able to manage its requisitioner database and approval system centrally, and it can use those systems seamlessly with multiple trading partners. Similarly, the selling organization can leverage a master catalog and order management system against multiple purchasers. In this ideal situation, information is not duplicated on either side.

Transaction Flow in the OBI Model

In this section, we walk through an OBI transaction. The descriptions in the following list correspond to the numbered arrows in Figure 6-8.

Figure 6-8FIGURE 6-8. OBI Transaction Flow

  1. The requisitioner uses a Web browser to connect to the buying organization's purchasing server and selects a hyperlink to the selling organization's catalog server.

  2. The selling organization's catalog server authenticates the requisitioner based on a digital certificate and then allows the requisitioner to browse, select items, and check out.

  3. The content of the order is transferred from the catalog server to the selling organization's OBI server.

  4. The sell-side OBI server maps the order into an OBI order request, encapsulated in an OBI object (with optional digital signature), and transmits the order request to the buying organization's OBI server over the Internet.

  5. The requisitioner specifies any necessary annotations to the order, and internal approval processes take place.

  6. The completed and approved order is mapped to an OBI order format, encapsulated as an OBI object, and transmitted back to the selling organization via the Internet.

  7. The selling organization obtains payment authorization, if necessary, and begins order fulfillment.

For additional information on OBI, see http://www.openbuy.org.

  • + Share This
  • 🔖 Save To Your Account

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