The client-server model is a distributed application structure that separates computing into two roles:
Communication happens over a network (LAN or WAN). The server is always on, listening for client requests. Clients connect when needed.
| Server type | Function | Example |
|---|---|---|
| Web server | Serves HTML/CSS/JS in response to HTTP requests | Apache, Nginx |
| File server | Centralised file storage/sharing over a network | NAS, Windows Server |
| Database server | Manages and queries databases | MySQL, PostgreSQL, SQL Server |
| Mail server | Sends/receives/stores email | Postfix, Exchange |
| DNS server | Resolves domain names to IP addresses | ISP DNS, Google 8.8.8.8 |
| Proxy server | Intermediary — caches content, filters, anonymises | Squid |
| Authentication server | Verifies user identity | Active Directory, LDAP |
| Print server | Manages print queue for network printers | Windows print server |
| Feature | Client-Server | Peer-to-Peer |
|---|---|---|
| Structure | Centralised — dedicated server | Decentralised — all equal peers |
| Security | Easier to secure — centralised control | Harder to secure — no central authority |
| Performance | Can scale with powerful server | Can degrade as more peers added |
| Administration | Centralised management | Each node manages itself |
| Cost | High (dedicated server hardware) | Low (uses existing hardware) |
| Use case | Business networks, websites | BitTorrent, some gaming |
Cloud computing delivers computing services over the internet (the "cloud") — servers, storage, databases, networking, software, analytics. Users pay on-demand rather than owning hardware.
| Model | You manage | Provider manages | Example |
|---|---|---|---|
| IaaS (Infrastructure as a Service) | OS, apps, data | Hardware, virtualisation, networking | AWS EC2, Azure VMs |
| PaaS (Platform as a Service) | Apps and data | OS, runtime, middleware, hardware | Heroku, Google App Engine |
| SaaS (Software as a Service) | Just use the app | Everything | Google Docs, Office 365, Gmail |
| Advantages | Disadvantages |
|---|---|
| Scalable — pay for what you use | Requires reliable internet connection |
| No upfront hardware cost | Ongoing subscription costs |
| Access from anywhere | Data may be stored in unknown locations |
| Provider handles maintenance and backups | Privacy/security concerns — data held by third party |
| Automatic software updates | Less control over infrastructure |
8 questions · instantly marked · AQA 7517 standard
| Term | Definition |
|---|
10 questions · 10 minutes