Full stack refers to working across all layers of a web application, from the user interface in the browser to the server code, database and deployment. A full-stack developer can build and debug each layer.
Why it matters
Real incidents rarely respect layer boundaries. A slow page might be a heavy script, an unindexed query or a misconfigured cache, and someone who understands the whole path finds the cause faster. Small teams often need people who can ship a feature from database table to button.
The term can also describe a technology bundle, such as a JavaScript front end with a Node.js back end and a SQL database.
Example
A single feature, saving a profile photo, touches every layer:
- Front end: a file input and upload progress bar.
- Back end: an endpoint that validates the file type and size.
- Storage: the image saved to disk or object storage, with its URL stored in a database row.
Common mistakes
- Believing full stack means expert at everything. It usually means competent across layers and deep in one or two.
- Ignoring operations: a feature is not finished until it is deployed, monitored and recoverable.
- Choosing a trendy stack with no one on the team who can debug it in production.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.