full-stack development
Building every layer of a web application yourself: the browser frontend, the backend server and API, and the database behind them.
In more detail
A full-stack engineer can follow one feature from a button in the browser, through the network request and server code, down to the database row it changes. Many production bugs live at the boundaries between these layers.
Related terms
- frontend — The part of a software system that runs in the user's browser or device and presents the interface.
- backend — The server-side part of a web application that stores data and produces responses, as opposed to the frontend that runs in the browser.
- API — A defined way for one program to ask another program to do something, such as a list of web requests a service accepts.
- database — A program that stores data in an organised way and answers questions about it, such as PostgreSQL.
Taught in
- Monorepo Architecture: Workspaces & Turborepo — Production Full-Stack Engineering
- End-to-End Type Safety: Shared Schemas & DTOs — Production Full-Stack Engineering
- Full-Stack System Verification: Capstone Integration — Production Full-Stack Engineering