Kudler Fine Foods Network
Feburary 28, 2013
Kudler Fine Foods Network
Overview and Timeframe
The many complexities of network design are vast, wide and most often tailored to the customer and their uses. In the case of Kudler Fine Foods the network is the backbone of the company compromising the bulk of communications as well as the point of sale network. The design of these networks is a collaborative procedure aimed at ensuring that the services provided meet the needs of the customer. In the search of the ideal plan for network development I will discuss and explain principles of distributed and centralized computer systems. Accomplishing this by describing different network topologies; the standards and protocols that are essential to networking. The responsibilities essential in providing telecommunication services to include security, privacy, reliability and performance. How we distinguish and understand the uses of voice over the internet protocol, Centrex and other forms of telecommunications. With our main goal is to develop a system to utilize in our company that will ensure a proper management of our resources. The timeline for this is to have an implemented plan in place within 30 days of commencement. Our outline of six months to have the plan implemented is not outside the rational. Considering the internal and external resources implemented in the project. Distributed Vs. Centralized
Comparing the principles of Distributed vs. Centralized computing systems and explaining some of the varying issues of each type. Both models have their own architectures and varying complexities with their own problems. I will be verifying the different types and how they interact. Distributed systems originally referred to a computer network that was physically and geographically located. Now the term is used to describe a process that run on a several systems and are interacting with each other by a physical connection. There are many different types of distributed systems and there is no one definition. However, there are a few guiding principles or commonalities that do define the group. First off it is made of several different computing systems that have their own memory and processor (Attiya & Welch, 2004). Each system communicates within itself by message passing. The system itself is lenient with malfunctions in distinct computers in the system. The structure of the system is unknown and may consist of varying information sources, and the system may change during the execution of distributed programing. However the major problems with distributed computing are consensus problems, and self-stabilization. The reliability is achieved by using synchronizers to run on asynchronous systems, logical clocks for providing an it happened before ordering system, and algorithms to synchronize clock management over time stamping. Conversely centralized computing is done at a central location. Most if not all of the peripherals will be handled by the host computer. It generally has dumb terminals or text only terminals or thin clients only with input output devices attached to the network. This offers greater security to the information stored on the system since it is mostly generated at the hub of the system and not at the terminal itself. In addition to security it has reliability in that if a terminal breaks down you can simply change out the devices or go to a new terminal and log in. Centralized computing is the most unsympathetic architecture of all because if the host or central system breaks down the whole system fails. This type of computing is not as contemporary as it once was, however, it is making a comeback due to the ability of cloud computing, and the total cost of ownership to a potential client is far less than other systems. Some systems utilize a hybrid system that runs remote desktop software that let the desktop run localized processes such as the web...
Please join StudyMode to read the full document