w2

Fat Clients and Servers.  Please respond to the following:

• Provide a scenario in which the use of fat servers would be preferred over the use of fat clients. Describe why fat servers, rather than fat clients, should be used in your scenario. 
• Compare the pros and cons of Intranets to those of the Internet from an organizational perspective. Suggest one way to integrate the two and the benefits this may bring.

Classmates:

Fat Clients and Servers.  Please respond to the following:

Provide a scenario in which the use of fat servers would be preferred over the use of fat clients. Describe why fat servers, rather than fat clients, should be used in your scenario.

Fat Client A user's computer that contains its own applications that are run in the machine. New programs are installed on the local hard disk. This is the typical way people use their computers. A fat client is:

●             Fat clients are the more traditional form of client/server.

●             The bulk of the application runs on the client side of the equation.

●             In both the file server and database server models, the clients know how the data is organized and stored on the server side.

●             Fat clients are used for decision support and personal software.

●             They provide flexibility and opportunities for creating front-end tools that let end-users create their own applications.

Fat Server: A server in a client/server environment that performs most or all of the application processing with little or none performed in the client. The counterpart to a fat server is a thin client. A fat server also:

●             Fat Server applications are easier to manage and deploy on the network because most of the code runs on the servers.

●             Fat servers try to minimize network interchanges by creating more abstract levels of service.

●             Transaction and object servers, for example, encapsulate the database.

●             The client in the fat server model provides the GUI and interacts with the server through remote procedure calls (or method invocations)

●             These are used for mission-critical applications, represent the new growth area from PC-based client/server computing.

A fat client (sometimes called a thick client) is a networked computer with most resources installed locally, rather than distributed over a network as is the case with a thin client. Most PCs (personal computers), for example, are fat clients because they have their own hard drive, DVD drives, software applications and so on.

Fat clients are almost unanimously preferred by network users because they are very customization and the user has more control over what programs are installed and specific system configuration. On the other hand, thin clients are more easily managed, are easier to protect from security risks, and offer lower maintenance and licensing costs.

A system that has some components and software installed but also uses resources distributed over a network is sometimes known as a rich client.

Compare the pros and cons of Intranets to those of the Internet from an organizational perspective. Suggest one way to integrate the two and the benefits this may bring.

Unlike many hyped-up trends, intranets make sense for small businesses. These internal Web sites provide an easy-to-reach and easy-to-update way to store the information employees require. Here are some reasons to create an intranet:

●             Your business uses several different types of computers - and the users all need to reach the same company information.

●             You need to centralize data in an easy-to-access way.

●             You'd like to give employees controlled use of more of the information stored on your network

●             You don't want to administer network versions of various software packages.

And here are reasons not to create an intranet:

●             You don't have a local area network, or your network's operating system - like some older versions of Novell NetWare - does not use TCP/IP, the Internet communications standard.

●             You don't have any compelling business justification for one.

●             Many of your employees don't use computers.

●             Nobody is available to set up and manage the intranet.

I know dealing with the internet vs. the intranet is that most companies do not have to deal with the 99.99 uptime rule. I have work with some companies where the net was down for more than 24 hours before a resolution was found.  This is bad practice when trying to save, retrieve, or modify archives. The bad this is that some companies have move their mail server off site with no access to a local host. So, communication becomes nonexistence.

The cool thing about thin clients is that it is more secure than fat clients. The reason for this is that fat client when most house whole people have does have the potential to spread viruses, become bots, and data can become corrupted. With thin clients incidents like this drops tremendously.

The best thing about the intranet is that it can be more organized. The databases at most of these companies use today is a lot more structurally sound than the internet. There are some cases where information from the internet is incorporates the intranet. But the information can be specific and to the point. The internet requires the use of a 3rd parity search engine such as Google or Bing to hope narrow down the and cross reference the information you are trying to locate. If a web link is dead, there is no IT staff to call to have that web link restore. You will have to go to a different DNS for a solution to your answer.

Pooneh sheini dashtgol

Reference:

Intranet Pros and Cons, Intranets and Extranets Article | Inc.com. (n.d.). Retrieved from http://www.inc.com/articles/1998/01/10226.html