Chapter 3: Introduction to Technological Aspects of Privacy
Client-Server Architecture: Front End and Back End
In the client-server model a client requests a service from a server. The browser-facing front end is separated from the back end databases; separating them helps contain a breach, protecting sensitive data even if the front end is compromised.
A client (desktop, laptop, phone) sends requests to a server. These interactions form the front end, generally coded in HTML, CSS, and JavaScript. The back end - databases and other computing not essential to operating the server - is often kept separate. A thick client processes data itself; a thin client relies on remote processing (e.g. a device running only a browser with Google Suite or Office 365).
🔑 Separation as a privacy control
Separating the front end and back end helps protect privacy and security. If a hacker plants malicious code on the front end and front/back interact only in limited, monitored ways, the back-end database stays better protected, reducing breach risk for sensitive personal information.
Key terms - quick answers
What is “Client”?
Hardware or software that accesses a service from a server by sending a request; a thick client processes data itself, a thin client relies on remote processing.
What is “Server”?
The computer process that responds to client requests, such as serving a news story or processing an order.
What is “Front end”?
The web-based interface where client and server interact, generally coded in HTML, CSS, and JavaScript.
What is “Back end”?
Devices and software operating separately from the web server, such as databases, that are not essential for operating the server.