Network Application Architectures

By: Imran Rashid
Submitted: 2009-11-12 18:00:36
Print this article | For publisher | Social Bookmarking
Rating:
 

Before diving into software coding, you should have a broad architectural plan for your application. Keep in mind that an application’s architecture is distinctly different from the network architecture. From the application developer’s perspective, the network architecture is fixed and provides a specific set of services to applications. The application architecture, on the other hand, is designed by the application developer and dictates how the application is structured over the various end systems. In choosing the application architecture, an application developer will likely draw on one of the two predominant architectural paradigms used in modern network applications: the client-server architecture or the peer-to-peer (P2P) architecture.

In a client-server architecture, there is an always-on host, called the server, which services requests from many other hosts, called clients. The client hosts can be either sometimes-on or always-on. A classic example is the Web application for which an always-on Web server services requests from browsers running on client hosts. When a Web server receives a request for an object from a client host, it responds by sending the requested object to the client host. Note that with the client- server architecture, clients do not directly communicate with each other; for example, in the Web application, two browsers do not directly communicate. Another characteristic of the client-server architecture is that the server has a fixed, well- known address, called an IP address (which we’ll discuss soon). Because the server has a fixed, well-known address, and because the server is always on, a client can always contact the server by sending a packet to the server’s address. Some of the better-known applications with a client-server architecture include the Web, F1’R Telnet, and e-mail.

Often in a client-server application, a single server host is incapable of keeping up with all the requests from its clients. For example, a popular social-networking site can quickly become overwhelmed if it has only one server handling all of its requests. For this reason, a cluster of hosts—sometimes referred to as a server farm—is often used to create a powerful virtual server in client-server architectures. Application services that are based on the client-server architecture are often infrastructure intensive, since they require the service providers to purchase, install, and maintain server farms. Additionally, the service providers must pay recurring interconnection and bandwidth costs for sending an4 receiving data to and from the Internet. Popular services such as search engines (e.g., Google), Internet commerce (e.g., Amazon and e-Bay), Web- based v-mail (e.g, Yahoo Mail), social networking (e.g., MySpace and Facebook), and video sharing (e.g., YouTube) are infrastructure intensive and costly to provide.

In a P2P architecture, there is minimal (or no) reliance on always-on infrastructure servers. Instead the application exploits direct communication between pairs of intermittently connected hosts, called peers. The peers are not owned by the service provider, but are instead desktops and laptops controlled by users, with most of the peers residing in homes, universities, and offices. Because the peers communicate without passing through a dedicated server, the architecture is called peer-to-peer. Many of today’s most popular and traffic-intensiye applications are based on P2P architectures. These applications include file distribution (e.g., BitTorrent), file searching/sharing (e.g., eMule and LimeWire), Intemet telephony (e.g., Skype), and IPTV (e.g., PPLive).

Imran Rashid has working knowledge about windows operating systems.For more information visit
Free CCNA Tests
Free Windows Certification

Article source: Expert Articles

Most Recent Articles in Wireless Networks category

  • Network Application Architectures - By: Imran Rashid
    Before diving into software coding, you should have a broad architectural plan for your application. Keep in mind that an application's architecture is distinctly different from the network architecture. From the application developer's perspective, the network architecture is fixed and provides a specific set of services to applications. The application architecture, on the other hand, is designed by the application developer and dictates how the application is structured over the various end systems
  • Networks Under Attack - By: Imran Rashid
    The field of network security is about how the bad guys can attack computer networks and about how we, soon-to-be experts in computer networking, can defend networks against those attacks, or better yet, design new architectures that are immune to such attacks in the first place.
  • Wireless Access - By: Imran Rashid
    Accompanying the current Internet revolution, the wireless revolution is also having a profound impact on the way people work and live. Today, more people in Europe have a mobile phone than a PC or a car. And the wireless trend is continuing with many analysts predicting that wireless (and often mobile) handheld devices -- such as mobile phones and PDAs-will overtake wired computers as the dominant Internet access devices throughout the world. Today, there are two common types of wireless Internet access.
  • Messages, Segments, Datagram's, and Frames - By: Imran Rashid
    The physical path that data takes down a sending end system's protocol stack, up and down the protocol stacks of an intervening link-layer switch and router, and then up the protocol stack at the receiving end system. As we discuss later in this book, routers and link-layer switches are both packet switches.
  • History of Computer Networking and the Internet - By: Imran Rashid
    You should know enough now to impress your family and friends! However, if you really want to be a big hit at the next cocktail party, you should sprinkle your discourse with tidbits about the fascinating history of the Internet.
  • Network Application Architectures - By: Imran Rashid
    Before diving into software coding, you should have a broad architectural plan for your application. Keep in mind that an application's architecture is distinctly different from the network architecture.
  • ISPs and Internet Backbones - By: Imran Rashid
    We saw earlier that end systems (user PCs, PDA's, Web servers, mail servers, and so on) connect into the Internet via an access network. Recall that the access network may be a wired or wireless local area network (for example, in a company, school, or library), a residential cable modem or DSL network, or a residential ISP (for example. AOL or MSN) that is reached via dial-up modem. But connecting end users and content providers into access networks -is only a small piece of solving the puzzle of connecting the hundreds of millions of end-systems and hundred of thousands of networks that make up the Internet.
  • File Transfer Protocol: FTP - By: Imran Rashid
    We have just learned that network processes communicate with each other by sending messages into sockets. But how are these messages structured? What are the meanings of the various fields in the messages.
  • How Do Packets Make Their Way Through Packet-Switched Networks? - By: Imran Rashid
    Earlier we said that a muter takes a packet arriving on one of its attached communication links and forwards that packet on to another of its attached communication links. But how does the router determine the link onto which it should forward the packet? This is actually done in different ways by different types of computer networks we will describe one popular approach, namely. The approach employed by the Internet. In the Internet, each packet traversing the network contains the address of the packet's destination in its header.
  • Upgrading your Network Hardware Infrastructure - By: Darwin Redshield
    Just like you want to learn about a date's likes and dislikes to see if there is potential for long term compatibility, you also need to carefully plan the integration of new and updated network hardware into your older structures.