Deal R Us Brokers Case Study
Chapter 2: Mini-Case I. Deals-R-Us Brokers (Part 1)
1. Classify the two alternatives in terms of what type of application architecture they use.
The first suggested solution is a client-based architecture since it’s the client that tells the server what data to select to analyze, making the client perform most of the work. The later architecture is a two-tier thin client architecture since it requires an application layer, in this case, a web browser and all processing is done by the server. 2. Outline the pros and cons of the two alternatives and make a recommendation to Fred about which is better.
Solution 1: Client-based pros-
1. Much more inexpensive to implement as micro-computers are considerably cheaper versus mainframe
2. Hardware …show more content…
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: 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.
2. Sometimes third party software may be required to translate between platforms via either Middleware or additional costs of development in adjusting client presentation to address the varying browsers and their implementations.
My recommendation is the thin-client solution. The server costs are minimal, allowing new servers to be added without affecting the existing infrastructure. Should a server go down and need replaced, a server can be removed, also without a significant impact on resources (assuming adequate servers existed to accommodate the amount of traffic experienced); using load balancing on the servers can help evenly distribute resource consumption. Finally, another advantage is using web browsers as clients. This reduces costs of having to deploy the application (addressing such issues as versioning), changes are reflected immediately when made on the
1. Classify the two alternatives in terms of what type of application architecture they use.
The first suggested solution is a client-based architecture since it’s the client that tells the server what data to select to analyze, making the client perform most of the work. The later architecture is a two-tier thin client architecture since it requires an application layer, in this case, a web browser and all processing is done by the server. 2. Outline the pros and cons of the two alternatives and make a recommendation to Fred about which is better.
Solution 1: Client-based pros-
1. Much more inexpensive to implement as micro-computers are considerably cheaper versus mainframe
2. Hardware …show more content…
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: 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.
2. Sometimes third party software may be required to translate between platforms via either Middleware or additional costs of development in adjusting client presentation to address the varying browsers and their implementations.
My recommendation is the thin-client solution. The server costs are minimal, allowing new servers to be added without affecting the existing infrastructure. Should a server go down and need replaced, a server can be removed, also without a significant impact on resources (assuming adequate servers existed to accommodate the amount of traffic experienced); using load balancing on the servers can help evenly distribute resource consumption. Finally, another advantage is using web browsers as clients. This reduces costs of having to deploy the application (addressing such issues as versioning), changes are reflected immediately when made on the