Full Stack Developer Terms Explained for Absolute Beginners

Web Development · Glossary

Full Stack Developer Terms Explained for Absolute Beginners

SECTION 01Frontend terms: what runs in the browser

The frontend is everything the user sees and interacts with in the browser. It is built with three core technologies — HTML for structure, CSS for appearance and JavaScript for behaviour. Frameworks such as React add their own words, but they all sit on top of these basics. If you understand the DOM and how JavaScript changes it, most frontend jargon starts to make sense.

<button id="greet">Say hello</button>
<p id="msg"></p>

<script>
  // The DOM lets JavaScript find and change elements
  document.getElementById("greet").addEventListener("click", () => {
    document.getElementById("msg").textContent = "Hello, full stack!";
  });
</script>

// A component is a function that returns UI
function Greeting({ name }) {
  return <h2>Hello, {name}!</h2>;
}

export default function App() {
  return (
    <div>
      <Greeting name="Asha" />
      <Greeting name="Rahul" />
    </div>
  );
}

SECTION 02Backend and API terms: the logic behind the scenes

The backend runs on a server. It receives requests, applies business rules, talks to the database and sends back responses. The bridge between frontend and backend is usually an API — a set of URLs (endpoints) that accept requests and return data, often as JSON. Understanding HTTP methods and status codes will help you read almost any backend tutorial.

from flask import Flask, jsonify, request

app = Flask(__name__)
products = [{"id": 1, "name": "Notebook", "price": 50}]

@app.get("/api/products")
def list_products():
    return jsonify(products)

@app.post("/api/products")
def add_product():
    item = request.get_json()
    item["id"] = len(products) + 1
    products.append(item)
    return jsonify(item), 201  # 201 = Created

if __name__ == "__main__":
    app.run(debug=True)

// Frontend JavaScript calling the backend API
fetch("/api/products")
  .then((res) => res.json())
  .then((data) => console.log(data));

fetch("/api/products", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({ name: "Pen", price: 10 }),
});

SECTION 03Database and deployment terms

Data has to live somewhere after the server restarts. Relational databases such as PostgreSQL and MySQL store data in tables, while document databases such as MongoDB store JSON-like documents. Backend frameworks often use an ORM so you can work with Python or JavaScript objects instead of raw SQL. Deployment terms describe how your app moves from your laptop to a server people can reach.

-- Raw SQL
SELECT name, price FROM products WHERE price < 100;

# Same idea with the Django ORM (Python)
Product.objects.filter(price__lt=100).values("name", "price")

import os

# Never hard-code secrets in your code or GitHub repo
DATABASE_URL = os.environ.get("DATABASE_URL", "sqlite:///dev.db")
SECRET_KEY = os.environ["SECRET_KEY"]  # fails loudly if missing

# On your machine:  export SECRET_KEY="change-me"
# On a host: set it in the hosting dashboard

SECTION 04Build your own full stack glossary

Keep a personal glossary as you learn. Writing a term in your own words is the fastest way to remember it.

Term:
Layer: Frontend / Backend / Database / Deployment
My own definition (one sentence):
Tiny example (code or real-life):
Where I saw it first:
Related terms:

Frontend : HTML, CSS, JavaScript, DOM, component, props,
           state, responsive, SPA
Backend  : server, route, endpoint, middleware, JSON,
           REST, authentication, authorisation
Database : table, row, primary key, foreign key, query,
           ORM, migration, index
Deploy   : domain, DNS, hosting, HTTPS, environment
           variable, build, CI/CD, logs

This week I learned these terms:
1.
2.
3.
Term I am still unsure about:
Small project where I will use it:

SECTION 05Tips for learning tech terms

You do not need to memorise a dictionary. These habits help terms stick:

• Learn terms in layers — frontend first, then backend, then database and deployment.
• Attach every term to code — a two-line example beats a long definition.
• Build one tiny full stack app — a to-do list with an API and database touches most core terms.
• Explain terms to someone else — teaching exposes the parts you have not understood.
• Read error messages slowly — they often contain the exact term you need to look up.

SECTION 06Interview Q&A — full stack terms

SECTION 07Test yourself — full stack terms quiz

SECTION 08Frequently asked questions

SECTION 09Related reads