Unit 2 Assignment
Michael Grube
Kaplan University Online
IT332 Principles of Information Systems Architecture
Professor Denver Martin
May 27, 2016

Table of Contents
Part 1: Examine the Three Architectures: Peer-to-Peer, Client/Server, and Web-based 3
Part 2: Propose One Architecture in Detail 4
Part 3: Examine and Explain the Role of Protocols for Your Proposed Architecture 5
Part 4: Explain and Detail the Supporting Infrastructure for the Proposed Architecture 6
References 7

Part 1: Examine the Three Architectures: Peer-to-Peer, Client/Server, and Web-based
A peer-to-peer network (P2P) is a network where all computers, workstations, and/or terminals are treated equally, i.e. the permissions and access is leveled across the board, and any one of the computers in the network can become the host (Englander, 2014). A way I worked this into my life was, while deployed, I set up a network where all computers connected to that network could share information and files as needed, so long as they were given access to the network in the first place. It was a small group, about 8 points of connection, using TCP/IP to communicate between the terminals, and was effective, however, I think we would have experienced some ‘bogging down’ of the network if we increased the number of people that had access to it. Because of the innate security risk that P2P networks exhibit, no sensitive information was permitted to be stored or shared on this network for any reason.
Client-server architecture is application based being installed a user’s computer or workstation (i.e. the ‘client’) and through that can make requests from the server, and save back to the server as needed. In this format, the client can perform tasks on data that remains on the server rather than on their personal workstation. Here, protocols include FTP, TCIP/IP, and IP, as this is how the information gets transferred to one location (client or server) to the other (Englander, 2014). This method also allows for rights to be granted to a client based on what the admin deems appropriate (like you see in Windows, you have options to limit what other users on a computer can do to any given document).
Now, web-based architecture is very similar to client-server, with the exception that it adds a web-server as a third layer. This allows the user to access and view web-based information, while being able to browse through and query data as though in a normal server. The protocols you will likely see inside this format are CGI (Common Gateway Interface), Hypertext Tansfer Protocol (HTTP and the secure variant, HTTPS) and XML (Extensible Markup Language) (Englander, 2014).
Part 2: Propose One Architecture in Detail
The architect that would be recommended would be normally dictated by cost, size, expansion levels for the future, as well as a need for security, and, being as how this is an alleged company that I am recommending this to, security is going to be a must, therefore, that takes P2P completely off the table as its noted lack of any real security functions would eliminate its viability as an option, in addition to the fact that P2P is better suited to very small, localized users. I would venture to go and say that the best possible option or combination therein would be a web-based architecture with some level of cloud-based computing option. This allows for a higher level of security management, as well as access to the web from an authorized terminal, as well as monitoring of user controls and access as needed, which is a necessary level of authentication to prevent intrusions and limit or mitigate the risks of internal threats to the company. In addition, the cloud computing option takes care of back-ups and storage, alleviating the cost of having to maintain that themselves. Displaced workers or worker abroad, with the web based service, would be able to utilize a virtual private networking option in order to access the information stored on the server from a remote location. This also doubles down on the security aspect, as the user much utilize a 2-step verification process in order to access the network from their respective location and giving the company a level of flexibility in terms of where and when they would be able to conduct business related tasks.
Part 3: Examine and Explain the Role of Protocols for Your Proposed Architecture
Given that incorporating web architecture is a two- and/or three-tier architecture (more likely three considering the obvious inclusion of a database), and the need for remote access will likely be present, I recommended the web-based architecture that incorporates HTML (to display the data on a web-based architecture), VoIP (for calls and conferencing), HTTP (another standard of information exchange on the web), TCP/IP (networking communications) (Englander, 2014), and this would be made possible through (depending on the actual physical configuration, through LAN’s and WAN’s (as needed, again, only depending on the configuration: WAN’s allow for less physical wiring, but can lack in security). SSL certificated would be a way of ensuring security and authentication when accessing the system.
Part 4: Explain and Detail the Supporting Infrastructure for the Proposed Architecture Like I mentioned, the physical layout and cost considerations would alter the necessary supporting infrastructure. If a wide space is used, or the company is located in an older building that frowns upon any modifications or additional wires being run, WAN’s and routers would be the key element, as running cables would not be cost effective or allowed, depending on the case, however, if it was permitted, and the space coverage wasn’t too great, a better option would be to simply run the Ethernet cables (CAT5e or CAT6) from the router/switch(s) to the various workstations. Again, this configuration is dependent on whether or not the server/database is going to be housed on site, off-site, or through a third party as a service, and what type of backup/file access system is put into place. Locally would incorporate more wires, off-site would be a bit more complicated with networked access, and a third party “as a service” option would likely be the simplest: they take care of backup and storage as well as security while allowing for easy authorized access from any location.
References
Englander, I. (2014). The architecture of computer hardware, systems software, & networking: An information technology approach (5th ed.). Retrieved from https://online.vitalsource. com/#/books/9781118803127