Lan Technologies Essay Example

the other hand, Option 2 utilizes a Thin Client architecture. In this scenario, there is little or no application logic installed on the client computer. Processing occurs on the server where the application is located. The user's workstation sends requests to this server for running the application.

The application will respond with information to the workstation, and only the display results need to be transmitted to the client. Users can connect via a web browser client over the internet or intranet without needing any executables on their workstations.
Question 2: Provide pros and cons of the two alternatives and recommend a better option to Fred.
Answer 2: Thick Clients require transferring larger amounts of data since processing occurs on each client machine.

When using a Thick Client, there are advantages and disadvantages. The benefits include improved application performance and a simpler development and implementation process. However, there is a disadvantage in that the application must be installed on every workstation and each workstation needs individual updates, which can be time-consuming. Tracking version control may also be challenging, and the application can face disruptions if users delete or modify its files. Furthermore, changes in the operating system may cause functional issues, requiring updates for different operating systems (32 bits, 64 bits). The update process for customers can also be time-consuming.

In contrast, Thin Clients are easier to manage because updates or changes only need to occur once on the server, granting all clients access to them. New clients simply require access permissions and the web address to use them. However, since Thin Clients rely on the client's browser, programming is necessary to ensure compatibility with popular browsers like Firefox,

Chrome, and Internet Explorer.

The advantages of utilizing a Thin Client include the ability for users to access the application from any supported browser via an intranet or the internet, easier implementation of application updates, restricted access to application files, and manageable versioning. Additionally, it eliminates the need for an additional hard disk and allows for centralized server support.

However, there are also disadvantages to using a Thin Client such as potential security difficulties when accessing the application through the internet, slower performance, dependency on the server's availability, and possible impact on application functionality due to browser changes. Furthermore, increased demands on the server and corporate network can lead to slower performance.

Despite these drawbacks, we recommend employing the Thin Client approach with a Client-Server based architecture as it offers various benefits over Thick Client architecture. It improves manageability, enables efficient data transfer, and ensures consistency in the user experience. This allows users to work regardless of their location within their company or even while traveling internationally. Due to hosting the application on the server-side, updates, configuration, and maintenance will incur lower costs since they only need to be done in one central location without repetition.

The distribution of the application can be expedited by simply setting up server-side access, which enables any user to access it. Additionally, the application can be configured with a failover server to minimize downtime and operational disruptions in case of an unexpected server failure.