Glossary

The words, without the shrug

Every term the courses use, defined in one line and then in a paragraph. Written to be read out of order.

Clear

Showing 8 of 8 matching “Port”

Agent

AI in the stack

A model that can take actions, not just produce text.

A language model given a set of tools it may call, allowed to loop: decide, act, look at the result, decide again. The important design question is not accuracy but blast radius: what the worst wrong action can reach.

See also Tool use, Blast radius, Prompt injection

Background job

Infrastructure

Work done after the response is sent.

Work moved out of the request so the user is not left waiting: sending email, processing an upload, generating a report. Requires somewhere to report progress and somewhere to report failure.

See also Queue, Worker, Cron

Deliverability

Infrastructure

Whether the mail you send reaches an inbox at all.

Sending is your side of it; delivering is the receiving provider’s decision, taken in a fraction of a second on the strength of what your domain says about you. Nothing in your code reports a failure here, which is why it is normally discovered by somebody who never got their password reset.

See also DNS, Transactional email, Bounce

Deprecation

Backend

Announcing that something will be removed.

Marking a field or endpoint as going away while still supporting it, so callers have time to move. Only meaningful if you can measure who is still using it.

See also Breaking change, Versioning

Full table scan

Data & Databases

Reading every row to answer one question.

What the database resorts to when no index supports your query. Instant with ten rows, catastrophic with ten million, which is why this problem never appears during development.

See also Index, Query

Port

Infrastructure

Which program on a machine you are talking to.

A number that lets one machine run many servers at once. The address finds the machine, the port finds the program: a web app on 3000, a database on 5432.

See also Server, localhost

Query

Data & Databases

A question asked of the database.

A request for data. Cheap when an index supports it, ruinous when it forces a scan of every row. Which questions you ask should be a design decision, not an accident.

See also Index, N+1, Full table scan

Tool use

AI in the stack

Letting a model call functions you define.

Giving a model a set of actions it may take: search, fetch, create. Turns a text generator into something that affects the world, which makes what you grant far more important than how well it reasons.

See also Agent, Blast radius