Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
67 views2 pages

Application Architecture Comparison

The first alternative uses a client-based architecture where a downloaded tool on the client communicates with the server to select and analyze data, which is then sent back to the client. The second alternative uses a two-tier client-server architecture where the application logic is partitioned between the client and server, with the server handling data and the client handling the application and presentation using a web browser. The client-based architecture has pros of lower cost and compatibility but cons of increased network traffic. The thin-client architecture has pros of better performance from load balancing and no deployment needed but a con of potential issues integrating different vendor software.

Uploaded by

eatspizza
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
67 views2 pages

Application Architecture Comparison

The first alternative uses a client-based architecture where a downloaded tool on the client communicates with the server to select and analyze data, which is then sent back to the client. The second alternative uses a two-tier client-server architecture where the application logic is partitioned between the client and server, with the server handling data and the client handling the application and presentation using a web browser. The client-based architecture has pros of lower cost and compatibility but cons of increased network traffic. The thin-client architecture has pros of better performance from load balancing and no deployment needed but a con of potential issues integrating different vendor software.

Uploaded by

eatspizza
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Drew Tadgerson Networking Concepts & Apps Mini-Case DEAL-R-US BROKERS Part 1 MIS589 January 13, 2013 Shaun

Gray

MINI CASE 1 DEAL-R-US BROKERS Questions A. Classify the two alternatives in terms of what type of application architecture they use. The first alternative in terms of application architecture is a client-based architecture. As it states that the downloaded tool will communicate with the DRUB server to select data and analyze, which is very similar to the client-based architecture where the clients tells the server what data to select and analyze and processes data will be sent back to the client for display. The second alternative in terms of application architecture is two-tier client-server architecture. The application logic can be partitioned between the client and the server. The server is responsible for the data and the client, the application and presentation. Using the web browser the client will talk to the web server using a standard called HTTP (Jerry Fitzgerald, 2009). B). Outline the pros and cons of the two alternatives and make a recommendation to Fred about which is better. Solution 1 Client-based architecture: Pros: 1. More inexpensive to implement as microcomputers are considerably cheaper versus mainframe. 2. Hardware of different manufactures or platforms can function together on the same network.

Solution 1 Client-based architecture: Cons: 1. Data traffic must be sent and received between client and host. 2. Due to the potential amount of information that must be sent between client and host, this can put a significant performance hit against the network, affecting all machines. Solution 2: Thin-client pros: 1. Better performance because processing is distributed to multiple machines (multiple web servers for example where load balancing is used to optimize network/server resources) 2. Using a web browser as the client for this architecture means no deployment is necessary. Presentation is changed on the server and is immediately reflected on all clients accessing the server. Hardware and software from different vendors can be (is possible) used together

Solution 2: Thin-Client-server cons: 1. Getting software from different vendors to work together smoothly can difficult to setup. Not all platforms implementations of web browser are universal; something that renders in Internet Explorer may look different or not render at all if client is using FireFox.

You might also like