Knowt
Note
Studied by 55 peopleNoteStudied by 20 peopleNoteStudied by 5 peopleNoteStudied by 16 peopleNoteStudied by 37 peopleNoteStudied by 19 people
Unit 2.2 Thin-Client vs Thick-Client Networks & Topologies
Aims
Explain the key characteristics of thin-client and thick-client computers.
Describe what is meant by the term network topology.
Explain what is meant by the term bus, star and mesh topology and the advantages and disadvantages of each.
Thin-Client Computers
Client thickness refers to processing and storing amount it does in comparison to connected server
Low powered computer connected to powerful central server.
Operating system (OS) and all programs run a virtual machine on the server
Thin-client computer only displays the output of the virtual machine and captures input from the user and send them to the virtual machine.
Features:
Minimal processing power, memory and storage capacity
Rely on network connection to access applications, data and processing resources from central server or cloud
More cost-effective than standard computers due to fewer components
Consume less power than standard computers due to lower hardware specifications
Used:
Want Central management of the network - e.g. want to install software and backups centrally
Cost Efficiency is important
Energy efficiency is important
Data-security is important
Thick-Client Computers (aka Fat-client)
OS and applications are run on actual computer
Thick-Client computers perform a lot of data processing and storage locally on computer itself
Features
Increased power processing, memory and storage capacity
More expensive than Thin-client as more powerful hardware
Have local storage e.g. hard drives/solid-state drives where data and applications are stored
Run applications and store data locally even when disconnected from network
Used
More processing power needed locally-e.g. if processing large volumes of data
Need to be able to work offline - access to applications without a network
Need greater flexibility - Users can install and run software locally/customise settings and manage local files with more flexibility than thin-client
Network Topologies
Physical or logical layout of a computer network, most common are:
Bus Topologies
Mesh Topologies
Star Topologies
Physical is where the cables are, logical is how the network works, e.g. physical star layout but bus logical layout
Bus Topologies
Each computer connects to a single line “The Backbone”
“Backbone” transmits data between the different devices on the network, data in packets are sent along the backbone and are only read by the devices that match the data packets address
Terminators (plugs) at either end of cable to stop signal bouncing
Best used - small no. of devices i.e small office/company
Pro’s | Con’s |
Simple and easy set-up and requires less tech knowledge and skill | No Scalability - overtime becomes more difficult to add devices to network |
Cheaper installation as it uses less cables | Single failure point, if the backbone breaks the network is paralysed |
Easier to troubleshoot if there is a network fault | Increased collisions as multiple devices may try and send data on the backbone at the same time (think bus trying to get on roundabout) |
Mesh Topologies
One computer passes data on to another using quickest route
Partially connected mesh - all computers connected but not directly
Full Mesh - all computers connected directly
Best used - Large scale co, e.g. monitoring patients/traffic lights etc.
Pro’s | Con’s |
No single failure point - self healing network, broken route? finds different one | Expensive installation if using wired setup or full mesh topology |
Adding to and modifying the network can be done without disruption | Network maintenance and admin is difficult, as it grows it can lack structure and become disorganised |
Data can be transferred from different devices simultaneously | Network type can have redundant connections |
Star Topologies
Computers connected directly to central point e.g. switch/server
All data passes through the central point
If one computer fails the other works but if the central point fails the computers cant communicate
Best used - Evolving network, devices +/- or heavy data traffic
Pro’s | Con’s |
Faster data transfer due to less collisions | Requires additional hardware e.g. switch/server |
If one computer fails the others still work | Single point of failure, central point fails, network is disrupted |
Easy scalability - easier to add to | Expensive due to every computer needing a cable to the central point |
Unit 2.2 Thin-Client vs Thick-Client Networks & Topologies
Aims
Explain the key characteristics of thin-client and thick-client computers.
Describe what is meant by the term network topology.
Explain what is meant by the term bus, star and mesh topology and the advantages and disadvantages of each.
Thin-Client Computers
Client thickness refers to processing and storing amount it does in comparison to connected server
Low powered computer connected to powerful central server.
Operating system (OS) and all programs run a virtual machine on the server
Thin-client computer only displays the output of the virtual machine and captures input from the user and send them to the virtual machine.
Features:
Minimal processing power, memory and storage capacity
Rely on network connection to access applications, data and processing resources from central server or cloud
More cost-effective than standard computers due to fewer components
Consume less power than standard computers due to lower hardware specifications
Used:
Want Central management of the network - e.g. want to install software and backups centrally
Cost Efficiency is important
Energy efficiency is important
Data-security is important
Thick-Client Computers (aka Fat-client)
OS and applications are run on actual computer
Thick-Client computers perform a lot of data processing and storage locally on computer itself
Features
Increased power processing, memory and storage capacity
More expensive than Thin-client as more powerful hardware
Have local storage e.g. hard drives/solid-state drives where data and applications are stored
Run applications and store data locally even when disconnected from network
Used
More processing power needed locally-e.g. if processing large volumes of data
Need to be able to work offline - access to applications without a network
Need greater flexibility - Users can install and run software locally/customise settings and manage local files with more flexibility than thin-client
Network Topologies
Physical or logical layout of a computer network, most common are:
Bus Topologies
Mesh Topologies
Star Topologies
Physical is where the cables are, logical is how the network works, e.g. physical star layout but bus logical layout
Bus Topologies
Each computer connects to a single line “The Backbone”
“Backbone” transmits data between the different devices on the network, data in packets are sent along the backbone and are only read by the devices that match the data packets address
Terminators (plugs) at either end of cable to stop signal bouncing
Best used - small no. of devices i.e small office/company
Pro’s | Con’s |
Simple and easy set-up and requires less tech knowledge and skill | No Scalability - overtime becomes more difficult to add devices to network |
Cheaper installation as it uses less cables | Single failure point, if the backbone breaks the network is paralysed |
Easier to troubleshoot if there is a network fault | Increased collisions as multiple devices may try and send data on the backbone at the same time (think bus trying to get on roundabout) |
Mesh Topologies
One computer passes data on to another using quickest route
Partially connected mesh - all computers connected but not directly
Full Mesh - all computers connected directly
Best used - Large scale co, e.g. monitoring patients/traffic lights etc.
Pro’s | Con’s |
No single failure point - self healing network, broken route? finds different one | Expensive installation if using wired setup or full mesh topology |
Adding to and modifying the network can be done without disruption | Network maintenance and admin is difficult, as it grows it can lack structure and become disorganised |
Data can be transferred from different devices simultaneously | Network type can have redundant connections |
Star Topologies
Computers connected directly to central point e.g. switch/server
All data passes through the central point
If one computer fails the other works but if the central point fails the computers cant communicate
Best used - Evolving network, devices +/- or heavy data traffic
Pro’s | Con’s |
Faster data transfer due to less collisions | Requires additional hardware e.g. switch/server |
If one computer fails the others still work | Single point of failure, central point fails, network is disrupted |
Easy scalability - easier to add to | Expensive due to every computer needing a cable to the central point |
NoteStudied by 55 peopleNoteStudied by 20 peopleNoteStudied by 5 peopleNoteStudied by 16 peopleNoteStudied by 37 peopleNoteStudied by 19 people