Terminology
Plain-language definitions of the words used across this learning series, from the browser all the way down to the database. Each term explains what it is and where it fits in the stack, so when you read about a request or a feature change you know exactly which layer the words are pointing at. Search the list or click a term to read its full definition.
Tech Stack Terminology
Click a term to read its definition.
API
Application Programming Interface. The set of addresses a front end can call to ask the server for information or to save changes, such as /contacts/42.
Authentication
Confirming who someone is, usually by checking their sign-in credentials or session before serving a request.
Authorization
Deciding what an signed-in person is allowed to do, such as whether they may view or edit a particular record.
Backend
Everything that runs on the company's servers rather than in the browser: the web server, the service layer and the database.
Browser
The program a person uses to open websites, such as Chrome or Safari. It downloads pages, applies styles and runs the front end code.
Business logic
The rules that make the software behave correctly for the company, such as 'a deal can only move forward to a stage that exists.'
Cache
A saved copy of information kept close at hand so the software does not have to fetch or compute it again. Caches make repeat requests faster.
Client
The side of an app that a person uses directly, usually the browser or a mobile app. It sends requests to the server side.
Content delivery network (CDN)
A network of servers around the world that stores copies of images, styles and scripts so they load quickly from a nearby location.
CRUD
Create, Read, Update, Delete. The four basic things software does to a stored record. Reading is the most common; deleting is handled with the most care.
Database
The software that stores the company's records on disk, such as customers, transactions or messages, and answers structured questions about them.
Database migration
A scripted change to the database's structure, such as adding a column, applied in a controlled way so existing data is not lost.
Deploy
Putting a new version of the software onto the servers people actually use. Deployments are usually automated and can be rolled back.
DNS
Domain Name System. The internet's address book: it translates a name like duckbuddy.net into the numeric address of a server.
Endpoint
One specific address in an API, such as POST /messages, that accepts a particular kind of request.
Front end
The part of an app that runs in the person's browser or on their phone: the screens, buttons, forms and the code that reacts to clicks.
Full stack
A shorthand for working across every layer at once: front end, service layer and database.
HTTPS
The encrypted version of the web's request protocol. It scrambles traffic between the browser and the server so others on the network cannot read it.
Index (database)
A lookup structure the database keeps so it can find records by a common field quickly, like the index at the back of a book.
JSON
JavaScript Object Notation. The text format most APIs use to send structured data back and forth, such as {"name": "Dana", "stage": "Demo"}.
Query
A request sent to the database, usually written in SQL, to read, add, change or remove records.
Request
One message a browser or app sends to a server asking for a page or an action, including its method, address and sometimes a payload.
Response
The server's reply to a request: a status code saying how it went, plus the page, data or error message.
REST
A common style for APIs where each address and HTTP method combination means one thing, such as GET /contacts to read and POST /contacts to create.
Schema
The structure of a database: which tables exist, which columns each has, and how the tables relate to each other.
Server
A computer (or a slice of one) that runs the company's software and answers requests from browsers around the clock.
Service layer
The code on the server that sits between the front end and the database. It checks who is asking, applies the business rules, and decides what to read or save.
SQL
Structured Query Language. The language used to talk to most databases, with statements like SELECT, INSERT, UPDATE and DELETE.
Status code
A short number the server puts on every response: 200 means success, 404 means not found, 500 means the server hit an error.
Tech stack
The set of technologies a company chose for each layer of its software, such as React for the front end, Go for the service layer and PostgreSQL for the database.
Validation
Checking that incoming data is acceptable before using it, such as a message being non-empty and under a length limit. Done on the server, not only in the browser.
Web server
The first program on the server side that receives HTTPS requests and sends them to the right part of the application.