🌌
Privacy Village Academy
Join The Community!AcademyAbout HGPE
  • Hitchhiker's Guide to Privacy Engineering
    • ❓What is HGPE?
      • ⚖️Who is this for?
      • 🧙‍♂️Privacy Engineering
      • 🎨Creative Privacy
      • 🔮Generative AI
      • 🧑‍💻About the Author
  • 🧙‍♂️The Ethical AI Governance Playbook 2025 Edition
    • 🤖Chapter 1 : AI Literacy
    • 🌍Chapter 2 : AI Governance in the 21st Century
    • ⌛Chapter 3 - Getting Started with AI Act Compliance
    • 🚀Chapter 4 : Rise of AI Governance: Building Ethical & Compliant AI
    • Chapter 5 : Introduction to the Lifecycle of AI
  • 🎓Privacy Engineering Field Guide Season 1
    • ❓Decoding the Digital World: Exploring Everyday Technology
    • 👁️Introduction: Why Privacy Matters?
      • Age of Mass Surveillance
      • Privacy & Democracy
      • Privacy & Government Surveillance
    • ⚡Chapter 1 : How Computers Work?
      • Electricity
      • Bits
      • Logic Gates
      • Central Processing Unit (CPU)
      • Graphic Processing Unit (GPU)
      • Motherboard
      • Data Storage
      • Databases
      • Operating System (OS)
      • Computer Code
      • Programming Languages
      • The File System
      • Bugs and Errors
      • Computer Virus
      • Internet of Things (IoT)
      • Cloud Computing
    • 🛰️Chapter 2 : How the internet works?
      • Physical Infrastructure
      • Network and Protocols
      • Switch
      • Routers
      • IP Address
      • Domain Name System (DNS)
      • Mac Address
      • TCP / IP
      • OSI Model
      • Packets
      • The Client - Server Architecture
      • Secure Socket Shell (SSH)
      • Transport Layer Security (TLS)
      • Firewall
      • Tunnels and VPNs
      • Proxy Server
    • 🖥️Chapter 3 : How Websites Work?
      • HTML
      • CSS
      • Javascript
      • Web Server
      • Browser
      • HTTP
      • Databases
      • Front End (Client Side)
      • Back End (Server Side)
      • Cookies
      • Local Storage
      • Session Storage
      • IndexedDB
      • XHR Requests
      • Web APIs
      • Webhooks
      • Email Server
      • HTTPS
      • Web Application Firewall
      • Single Sign-on (SS0)
      • OAuth 2.0
      • Pixels
      • Canvas Fingerprinting
      • Email Tracking
      • Containers
      • CI/CD
      • Kubernetes
      • Serverless Architecture
    • ⚛️Chapter 4 : How Quantum Computers Work?
      • Quantum Properties
      • Quantum Bits (Qubits)
      • Decoherence
      • Quantum Circuits
      • Quantum Algorithms
      • Quantum Sensing
      • Post-Quantum Cryptography
    • 📳Chapter 5 : Mobile Apps and Privacy
      • Battery
      • Processor
      • Mobile Operating Systems
      • Mobile Data Storage
      • Cellular Data
      • Mobile Device Sensors
      • Wireless Connectivity
      • Camera & Microphone
      • Mobile Apps
      • Software Development Kits (SDKs)
      • Mobile Device Identifiers
      • Bring Your Own Device (BYOD)
  • 🕵️‍♂️Privacy Engineering Field Guide Season 2
    • ❓Introduction to Privacy Engineering for Non-Techs
      • 🎭Chapter 1 : Digital Identities
        • What is identity?
        • Authentication Flows
        • Authentication vs. Authorization
        • OAuth 2.0
        • OpenID Connect (OIDC)
        • Self Sovereign Identities
        • Decentralized Identifiers
        • eIDAS
      • 👁️‍🗨️Chapter 2 : De-Identification
        • Introduction to De-Identification?
        • Input / Output Privacy
        • De-identification Strategies
        • K-Anonymity
        • Differential Privacy
        • Privacy Threat Modeling
  • 📖HGPE Story and Lore
    • 🪦Chapter 1 : The Prologue
    • ☄️Chapter 2 : Battle for Earth
    • 🦠Chapter 3 : A Nightmare To Remember
    • 🧙‍♂️Chapter 4 : The Academy
    • 🌃Chapter 5: The Approaching Darkness
    • ⚔️Chapter 6 : The Invasion
    • 🏰Chapter 7 : The Fall of the Academy
    • 🛩️Chapter 8 : The Escape
    • 🪐Chapter 9 : The Moon Cave
    • 🦇Chapter 10: Queen of Darkness
  • 📺Videos, Audio Book and Soundtracks
    • 🎧Reading Episodes
    • 🎹Soundtracks
  • 👾HGPE Privacy Games and Challenges
    • 🎮Data Privacy Day'23 / Privacy Treasure Hunt Game
    • 🧩Privacy Quest
  • 📬Subscribe Now!
Powered by GitBook
On this page
  • What is a Client-Server architecture?
  • What does the server do?
  • What does the client do?
  • How do they talk?
  • Privacy Risks

Was this helpful?

  1. Privacy Engineering Field Guide Season 1
  2. Chapter 2 : How the internet works?

The Client - Server Architecture

PreviousPacketsNextSecure Socket Shell (SSH)

Last updated 2 years ago

Was this helpful?

What is a Client-Server architecture?

The client-server approach enables any general-purpose computer to expand its capabilities by utilizing the shared resources of other computers it is connected via a network.

A client-server network allows computers such as mobile phones or laptops to access resources and services from a central computer on the Internet. This is what happens when you log in to servers located in the data centers of social media platforms or any games or cloud services that you use on daily basis.

A major advantage of the client-server network is the central management of applications and data, where the rise of has emerged.

What does the server do?

The server that you connect to handles things like querying and interacting with its database, accessing files on a server, interacting with other servers, processing your inputs, and structuring web applications.

What does the client do?

Client-side refers to the specific app, social media platform, or website you are running on your computers.

The client is used for sending requests to the central server on your behalf. It helps you access the content you would like to see such as the user interface and do other stuff like reading and/or writing cookies, interacting with local storage, interacting with temporary storage, creating interactive web pages, and functions as an interface between client and server.

How do they talk?

The client-server relationship communicates in a request–response messaging pattern and must adhere to a common communications protocol. Client-server communication typically adheres to the protocol suite.

Privacy Risks

Today, centralized app nodes are controlled and operated by the planet’s richest organizations, collecting and storing billions of people’s data.

Data stored in a huge centralized database is quite vulnerable. Hackers need to break through just one system to compromise valuable user data. Often, the data is being used to to serve them better ads.

Centralized client-server architecture is not healthy as it allows a cluster of servers or a core decision-making entity or individual to have all the power within the system.

As the internet became more centralized and commercial, the risks of living lives inside the servers of tech giants were more apparent than ever, especially for vulnerable groups such as children.

Social media defines the experience of being online on Web 2. These social media products and services are handling billions of users' data to generate inside their centralized computers.

The constant invasion of privacy and unfair censorship of choosing the narratives of what content is being shown to users has even been used to .

A Web 2 social media site, for instance, can censor any news, post, or tweet at any time they want to create

cloud computing
TCP/IP
micro-segment individuals
big data
sabotage democracies
filter bubbles and echo chambers.
🎓
🛰️
Page cover image