Full-Stack Lexicon.

A set of protocols and tools for building software applications. It specifies how software components should interact.

A methodology for building design systems that breaks UIs into fundamental components (atoms, molecules, organisms).

A cloud-computing model where developers outsource all the behind-the-scenes aspects of a web or mobile application.

A method to frequently deliver apps to customers by introducing automation into the stages of app development.

The process of bundling an application together with its related configuration and dependencies so it can be run in different computing environments.

A technique where the browser downloads a minimal HTML page and then uses JavaScript to render the content.

Software for creating and managing databases, providing users and programmers with a systematic way to create, retrieve, update, and manage data.

A set of practices that combines software development (Dev) and IT operations (Ops) to shorten the systems development life cycle.

A programming interface for web documents. It represents the page so that programs can change the document structure, style, and content.

A distributed computing paradigm that brings computation and data storage closer to the sources of data.

The practice of working on both the front-end and back-end portions of an application.

A query language for APIs and a runtime for fulfilling those queries with your existing data.

A back-end-only content management system that makes content accessible via an API for display on any device.

The process of attaching event listeners to the DOM nodes rendered on the server to make them interactive in the browser.

The managing and provisioning of infrastructure through code instead of through manual processes.

A compact, URL-safe means of representing claims to be transferred between two parties.

An open-source system for automating deployment, scaling, and management of containerized applications.

An architectural style that structures an application as a collection of small, autonomous services modeled around a business domain.

The traditional unified model for software program design, where all components are interconnected and interdependent.

A non-relational database that provides a mechanism for storage and retrieval of data modeled in means other than tabular relations.

A programming technique for converting data between incompatible type systems using object-oriented programming languages.

A type of application software delivered through the web, built using common web technologies including HTML, CSS, and JavaScript.

A software architectural style that defines a set of constraints to be used for creating Web services.

A software licensing and delivery model in which software is licensed on a subscription basis and is centrally hosted.

A cloud-computing execution model in which the cloud provider runs the server and dynamically manages the allocation of machine resources.

A technique where the server generates the full HTML for a page and sends it to the client.

The process of pre-rendering a website into static HTML files at build time.

A concept in software development that reflects the implied cost of additional rework caused by choosing an easy solution now instead of a better approach.

The extent to which a programming language discourages or prevents type errors, often via a compiler.

A level of software testing where individual units or components of a software are tested.

A person's emotions and attitudes about using a particular product, system, or service.

Adding more power (CPU, RAM) to an existing server, as opposed to adding more servers.

A binary instruction format for a stack-based virtual machine, designed as a portable compilation target for programming languages.

A TypeScript-first schema declaration and validation library with static type inference.