Tech Stack Impact Explorer

Learn the Words Behind the Tech Stack

  • Search plain-language definitions of the words developers use for the browser, the server, the database, and everything in between — from API, HTTPS and DNS to queries, schemas and status codes.
  • Click any term to read its definition, then jump back into the other pages and see where it fits in the stack!

Tech Stack Terminology

Click a term to read its definition.

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.

Confirming who someone is, usually by checking their sign-in credentials or session before serving a request.

Deciding what an signed-in person is allowed to do, such as whether they may view or edit a particular record.

Everything that runs on the company's servers rather than in the browser: the web server, the service layer and the database.

The program a person uses to open websites, such as Chrome or Safari. It downloads pages, applies styles and runs the front end code.

The rules that make the software behave correctly for the company, such as 'a deal can only move forward to a stage that exists.'

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.

The side of an app that a person uses directly, usually the browser or a mobile app. It sends requests to the server side.

A network of servers around the world that stores copies of images, styles and scripts so they load quickly from a nearby location.

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.

The software that stores the company's records on disk, such as customers, transactions or messages, and answers structured questions about them.

A scripted change to the database's structure, such as adding a column, applied in a controlled way so existing data is not lost.

Putting a new version of the software onto the servers people actually use. Deployments are usually automated and can be rolled back.

Domain Name System. The internet's address book: it translates a name like duckbuddy.net into the numeric address of a server.

One specific address in an API, such as POST /messages, that accepts a particular kind of request.

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.

A shorthand for working across every layer at once: front end, service layer and database.

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.

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.

JavaScript Object Notation. The text format most APIs use to send structured data back and forth, such as {"name": "Dana", "stage": "Demo"}.

A request sent to the database, usually written in SQL, to read, add, change or remove records.

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.

The server's reply to a request: a status code saying how it went, plus the page, data or error message.

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.

The structure of a database: which tables exist, which columns each has, and how the tables relate to each other.

A computer (or a slice of one) that runs the company's software and answers requests from browsers around the clock.

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.

Structured Query Language. The language used to talk to most databases, with statements like SELECT, INSERT, UPDATE and DELETE.

A short number the server puts on every response: 200 means success, 404 means not found, 500 means the server hit an error.

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.

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.

The first program on the server side that receives HTTPS requests and sends them to the right part of the application.

Where to Go Next

Keep going in order, or jump to any page from the top menu.