# Client Server & Peer to Peer ## Client-Server Networks ### What is a client-server network? - **Powerful server machines** manage and control the network, providing services to **client computers** - Clients request and consume resources from the servers - The server acts as the central hub that: - Hosts resources and data - Delivers services to clients - Manages most network operations - Examples of services: file storage, email hosting, web hosting, database access, authentication

A client-server network is an architecture where dedicated server computers provide resources and services to multiple client devices

### Benefits of client-server networks - **Centralised management**: All resources, updates, and security policies controlled from one location - Think of it like a school library where the librarian (server) manages all books and lending from a central desk - **Scalability**: Adding new client devices is straightforward without major reconfiguration - New computers can simply connect and access existing services - **Enhanced reliability**: Resources managed centrally means better consistency and availability - Regular backups and maintenance performed centrally - Professional server hardware typically more robust than desktop machines - **Security**: Centralised control allows for stronger security measures - User permissions managed from central location - Data stored securely on servers rather than scattered across devices ### Drawbacks of client-server networks - **Single point of failure**: If the server goes down, services become unavailable - Like a coffee shop where everything stops if the espresso machine breaks - Mitigation: Use redundant servers or backup systems - **High costs**: Expensive to implement and maintain - Server hardware more costly than standard computers - Often requires dedicated IT staff for administration - Software licensing for server operating systems - **Complexity**: Requires technical expertise to set up and manage - Network administrators needed for maintenance - More complex troubleshooting when issues arise ### When to use client-server networks | **Scenario** | **Why Client-Server Works Well** | |--------------|----------------------------------| | Large organisations (50+ users) | Centralised management becomes essential at scale | | Businesses requiring high security | Centralised control over access and data protection | | Environments needing reliability | Professional-grade servers provide better uptime | | Shared resource access | Multiple users accessing same databases or files | | Regulated industries | Easier to maintain compliance with central control |

Client-server is ideal when reliability, security, and centralised management outweigh the higher setup costs

--- ## Peer-to-Peer Networks ### What is a peer-to-peer network? - The **simplest network architecture** with no hierarchy between devices - **All computers have equal status** and responsibility - No dedicated server - Each machine acts as both client and server - **Distributed responsibility**: Each user manages their own machine - Individual users handle security, backups, updates - Data stored locally on individual devices - **Direct communication**: Computers connect and share resources directly with each other - Think of it like a study group where everyone brings their own notes to share, rather than one person being in charge

A peer-to-peer network is an architecture where all connected devices share equal responsibility without a central server

### Benefits of peer-to-peer networks - **Easy setup**: No complex server configuration required - Can be established in minutes with basic networking knowledge - Like setting up a group chat rather than building a website - **Lower cost**: No expensive server hardware or administrative staff needed - Standard desktop/laptop computers sufficient - No server software licensing costs - **No single point of failure**: Network continues functioning if one machine goes down - Other peers remain operational - Like a study group that continues even if one person is absent - **Direct data sharing**: Files transferred directly between devices without intermediary - Can be faster for local file transfers - No server bottleneck ### Drawbacks of peer-to-peer networks - **Security vulnerabilities**: Lack of centralised control creates risks - Each device is a potential entry point for threats - No unified security policy enforcement - Like having multiple doors to a building with different locks on each - **Not scalable**: Performance degrades with larger networks - Each device manages its own connections - Network becomes chaotic with many peers (typically problematic beyond 10-20 devices) - **Inconsistent availability**: Resources only accessible when host device is on - If someone shuts down their computer, their shared files become unavailable - **Management complexity**: No centralised administration - Each user responsible for their own backups and security - Difficult to enforce policies or standards across the network ### When to use peer-to-peer networks | **Scenario** | **Why Peer-to-Peer Works Well** | |--------------|----------------------------------| | Home networks | Simple setup for few family devices | | Small businesses (under 10 users) | Cost-effective for limited users | | Temporary file sharing | Quick collaboration without infrastructure | | Budget constraints | When funds don't allow for server investment | | Casual collaboration | When formal management isn't required |

Peer-to-peer networks become increasingly difficult to manage and secure as they grow beyond 10-15 devices

--- ## Comparing Client-Server and Peer-to-Peer | **Aspect** | **Client-Server** | **Peer-to-Peer** | |------------|-------------------|------------------| | **Cost** | High initial investment and ongoing maintenance | Low cost, minimal hardware requirements | | **Scalability** | Excellent - easily handles hundreds of clients | Poor - struggles beyond 10-20 devices | | **Security** | Strong - centralised control and policies | Weak - distributed responsibility creates vulnerabilities | | **Reliability** | High - professional server hardware | Moderate - dependent on individual peer availability | | **Management** | Centralised - single point of administration | Distributed - each user manages own device | | **Performance** | Consistent - dedicated server resources | Variable - depends on individual peer specifications | | **Setup complexity** | High - requires technical expertise | Low - basic networking knowledge sufficient | | **Single point of failure** | Yes - server failure affects all users | No - network continues with remaining peers | | **Best for** | Large organisations, high security needs | Home networks, small groups, temporary sharing |

The choice between architectures depends on organisation size, budget, security requirements, and technical expertise available

### Decision factors - **Number of users**: - Under 10 users → Peer-to-peer viable - 10-50 users → Client-server recommended - 50+ users → Client-server essential - **Security requirements**: - Sensitive data or regulatory compliance → Client-server - Casual file sharing → Peer-to-peer acceptable - **Budget**: - Limited funds → Peer-to-peer - Budget for infrastructure → Client-server - **Technical expertise**: - No IT staff → Peer-to-peer - Dedicated administrators → Client-server - **Resource access patterns**: - Shared databases or frequent collaboration → Client-server - Occasional file sharing → Peer-to-peer ### Hybrid approaches - Some networks combine both architectures: - Client-server for critical services (email, databases, authentication) - Peer-to-peer for direct file transfers between users - Example: Office network with central file server, but users can also share documents directly for quick collaboration