Nine spreads. One picture each. By the last page you can explain, in an interview or a meeting, how a click on a button turns into a row in a database and back into pixels.
"It's a three-tier app: a React frontend, a REST API on Node, Postgres underneath, all containerized and deployed behind a reverse proxy with TLS."
Every word in that sentence gets its own page. Use the tabs above or the arrow keys.
GET /products HTTP/1.1 with headers and cookies.200, 404, 500) plus HTML or JSON.The frontend runs inside the user's browser. Its job: show data and collect input. It never holds secrets.
<form id="signup">
<input name="email" type="email" required>
<button>Join</button>
</form>
<script>
signup.onsubmit = async (e) => {
e.preventDefault();
await fetch("/api/users", {
method: "POST",
headers: {"Content-Type": "application/json"},
body: JSON.stringify({ email: e.target.email.value })
});
};
</script>
fetch and updates the page."It's a responsive SPA; components fetch from the API and we keep accessibility in mind with semantic markup."
The backend runs on your machine, not the user's. It validates input, enforces rules, talks to the database, and holds the secrets (API keys, DB passwords).
// Node + Express
import express from "express";
const app = express();
app.use(express.json()); // middleware
app.post("/api/users", async (req, res) => {
const { email } = req.body;
if (!email?.includes("@"))
return res.status(400).json({ error: "bad email" });
const user = await db.user.create({ data: { email } });
res.status(201).json(user);
});
app.listen(3000);
/users, /orders/:id)."The API is stateless and RESTful; auth is a middleware, and controllers stay thin with logic in a service layer."
Servers restart; data must not vanish. The database is the permanent store. Only the backend talks to it.
CREATE TABLE users ( id SERIAL PRIMARY KEY, email TEXT UNIQUE NOT NULL, pw_hash TEXT NOT NULL, created_at TIMESTAMPTZ DEFAULT now() ); SELECT u.email, SUM(o.total) FROM users u JOIN orders o ON o.user_id = u.id GROUP BY u.email;
Rule zero: never trust the client. Anything from the browser can be faked. Re-check it all on the server.
HttpOnly; Secure; SameSite cookies, or JWTs, or OAuth "Sign in with Google".// ✗ injectable
db.query(`SELECT * FROM users WHERE email='${email}'`)
// ✓ parameterized
db.query("SELECT * FROM users WHERE email=$1", [email])
"We follow the OWASP Top 10: parameterized queries, hashed creds, least privilege, CSP headers, and secrets out of the repo."
A framework hands you routing, structure, and conventions so you write only the parts unique to your app. A stack is the combo you pick.
"We went with Next.js for SSR and SEO, Prisma as the ORM, Postgres on a managed host. It keeps the team in TypeScript end to end."
A server is just a computer that's always on and reachable. You rent one; you don't buy one.
# Dockerfile FROM node:20-alpine WORKDIR /app COPY package*.json ./ RUN npm ci --omit=dev COPY . . EXPOSE 3000 CMD ["node", "server.js"]
A record at your server's IP."CI builds a Docker image on merge to main, pushes to a registry, and we roll it out behind a load balancer with zero-downtime deploys."
POSTs JSON over HTTPS.my-app/ ├─ frontend/ React (Vite) → built to static files ├─ backend/ Express API, routes/, services/ │ └─ prisma/ schema + migrations ├─ docker-compose.yml api + postgres locally ├─ .env.example DATABASE_URL, SESSION_SECRET └─ .github/workflows/deploy.yml
fetch to it."Frontend shows, backend thinks, database remembers, security guards, servers host, frameworks speed it up, and CI/CD ships it."