Developer Glossary

A set of rules that lets one piece of software communicate with another.

The server-side part of an application that handles logic, data and business rules.

Continuous Integration and Continuous Delivery — automating build, test and release steps.

A lightweight, isolated unit that packages an application with its dependencies.

An organized collection of structured data, typically accessed via SQL or a driver.

A specific URL where an API can be accessed by a client.

A pre-built structure of code that provides a foundation for building applications.

The client-side part of an application that users see and interact with.

A distributed version control system for tracking changes in source code.

The protocol used to transfer data between clients and servers on the web.

JavaScript Object Notation — a lightweight, human-readable data-interchange format.

Code that runs between a request and a response, often for logging or auth checks.

Object-Relational Mapping — a technique for querying databases using objects instead of raw SQL.

A storage location for a project's code and its full version history.

An architectural style for designing networked APIs around resources and HTTP verbs.

The environment in which a program executes, e.g. Node.js for JavaScript.

A defined structure describing how data is organized in a database or API.

A piece of data used to authenticate or authorize a request without sending a password.

A system for tracking and managing changes to code over time.

An automated HTTP callback triggered by an event in another system.