HRM 3450 Chapter 19: HRM 3450 Chapter 19 Notes
HRM 3450 Chapter 19 Notes – Summary
Introduction
• The system can be scaled easily by adding more computers.
• Finally, the failure of a PC does not result in failure and, in fact, has minimal effect on
the performance of the system overall.
• Thus, this solution meets the original requirements admirably.
• It is worth noting that a fundamental understanding of computer infrastructure was key
to the syste architects’ solutio.
• This discussion provides a simple overview of the Google system.
• Hopefully you found even this brief look at the Google system interesting and
informative.
• There are a number of other considerations in the Google system architecture that we
have glossed over for now.
• However, to understand the Google architecture better, it is first necessary to continue
our exploration of the hardware, software, and network components that make up the
Google system, as well as every other IT system.
• We will return for a more in-depth discussion of the Google system architecture in
Supplementary.
• When working with large concepts with defined boundaries, it is often easiest to think
of them in terms of systems.
• A system can be defined as a collection of components, linked together and organized in
such a way as to be recognizable as a single unit.
• The components themselves may also be recognized as subsystems, to be further
reduced into components, when appropriate.
• The area outside the boundaries of a system is its environment.
• The system affects and is affected by various elements of the environment.
• In many situations, the environment supplies inputs to the system and receives outputs
from the system.
find more resources at oneclass.com
find more resources at oneclass.com