Executive Summary

The ever changing world of information technology has its disadvantages and advantages.  One advantage, being the ability to have numerous options when developing a strong system architecture that works well for everyone involved.  Whether employees are physically onsite and in the office or offsite working from home or on the go, we can provide them with a fully functional system wherever the job takes them.  Considering, we have the ability to enhance our network with the technological devices available in today's world, why not start today?  First we will discuss the few architecture options available such as peer-to-peer, client-server, and web-based computing; then I will make a recommendation based on our findings.

“Peer-to-peer architecture treats the computers in a network as equals, with the ability to share files and other resources and to move them between computers.” (Englander, 2014)  This may seem like a great scenario considering it is easy to send and share files with each other, but it can be extremely unsecure and cause major damage if someone's device is infected with a virus.  The client-server system is a workstation communicating with a server for specific actions such as an e-mail, database, or files.  This system would allow security and protection when accessing files from the computer to the server, whereas the peer-to-peer would not. 

A web-based computing system is specifically a computer communicating with a web server to perform tasks through services over the internet.  “The user of a Web-based system interacts with the system using a standard Web browser, enters data into the system by filling out Web-style forms, and accesses data using Web pages created by the system in a manner essentially identical to those used for the Internet.” (Englander, 2014)  This system depends on the network being online 100% of the time which is not likely.  When it comes to security, web-based is not as nearly secure as the client-server system, but is a bit more secure than the peer-to-peer system.

The client-server architecture is the most commonly used system across the region, as it is secure, efficient, and easy to maintain.  The main server would be the domain controller with a terabyte SATA hard drive installed, which contains active directory that allows the server administrator to maintain user accounts, their security profiles, and the corresponding device profiles.  The ability to assign security profiles to each employee restricts access to files and servers they do not need to perform their job.  A firewall and anti-virus software would be setup on the domain controller server so all of the shared files and their respective devices on the domain would be protected and monitored over HTTP and TCP/IP, throughout the company.  Some file exclusions may be setup on the anti-virus software to ensure databases are not corrupted by the scans performed.  The ability to manage updates and patches on multiple devices can be complicated at times, but if we implement network management software we can easily keep an eye on all devices, network performance, and any patches available.  This software can even assist in performing regular updates with schedule tasks.

A protocol specification defines such communication features as data representation, signaling characteristics, message format, meanings of messages, identification and authentication, and error detection. Protocols in a client–server system assure that requests are understood and fulfilled and that responses are interpreted correctly.

  There can even be a server setup specifically for each department within the company, such as a web, file, database, e-mail, and application server.  A file sharing server would maintain all the companies' files and allow each computer/client access simultaneously.  Each and every employee would be able to use the same exact version of the software to access the files.  An external backup performed nightly would eliminate any data loss and downtime spent, if something were to happen to the file server.  Another server could contain the company's database and only certain employees within the company would have access to the database to ensure security. 

In order for the client computers to communicate with the servers we would require networking equipment.  At the front line there is a secure router with a switch connected to it,  that maintains the MAC address of every device on the network and their associated static IP addresses.  This setup would allow the networking team to monitor the devices that access the network at any given point in time.  Each department would have their networking cables dropped through their cubicles and connecting to a switch that communicates with the router.  Respectively speaking, each computer would be directly connected to the switch with Ethernet cables that communicate with the router and down to the server.  Once it has reached the server to receive the information needed it takes the fastest route back to send the requested data to the computer.

Overall, client-server architecture is the most commonly used because it is easier to implement and maintain.  Once web-based computing becomes more feasible and secure other companies may take the initiative to switch.  Luckily, if a company currently utilizes a client-server architecture, it will be quite easy to make the switch with minimal downtime when web-based becomes safer.

References

Englander, I. (2014). The Architecture of Computer Hardware, Systems Software, & Networking An information technology approach. Don FowleY.

Posey, B. (2000, May 26). Understanding the differences between client/server and peer-to-peer networks. Retrieved February 11, 2017, from Tech Republic: http://www.techrepublic.com/article/understanding-the-differences-between-client-server-and-peer-to-peer-networks/

Smith, D. (2003, January). Multi-tiered Architectures and Applications Servers. Retrieved February 11, 2017, from Tokyo PC: http://www.tokyopc.org/newsletter/2003/01/arch_n_app_servers.html