Full stack

The "stack" is the set of technologies a project is built on, layered like a stack: the front end at the top, then the back end code, the database and the server underneath. A full-stack developer can work on all of them, and a full-stack framework provides tools for all of them in one package.

Full stack does not mean expert in everything. It usually means comfortable across the layers and deeper in one or two. For a small business site that breadth is often exactly what is needed; for a large or specialised product, separate front-end and back-end specialists may do better work.

How it works

A full-stack developer can take a feature from idea to launch on their own. For a new enquiry form, that means building the form people fill in, writing the server code that checks and processes it, designing the database table that stores it, connecting the email notification and setting up the deployment that puts it live.

The advantage is that nothing gets lost between people. A front-end developer and a back-end developer working separately have to agree on exactly what data passes between them; one person holding both ends can change both at once. The cost is depth. Areas such as performance tuning at scale, complex interface animation or security hardening reward specialists who do nothing else.

Some stacks have names made from the initials of their parts, such as the operating system, web server, database and programming language they combine. The name matters less than whether the pieces are well supported, suit the project and can be run on hosting you are happy to pay for.

Example

A small association wants a members' area where members log in, update their details and download meeting documents. One full-stack developer builds the login screen, the profile page, the server logic that checks who can see which files and the database behind it.

There is no handover between teams, so when the board asks for a new "paid until" date on each profile, the developer adds the database field, the admin screen and the member view in an afternoon. The weak point is what happens when that developer moves on, because often nobody else knows where the code lives or how to deploy it.

When the developer does leave a year later, the association avoids a rebuild because it had insisted on two things at the start: the code was kept in a repository under the association's own account, and the developer wrote a one-page note on how to run and update the site. A new developer reads the note, gets the site running locally in a day and carries on where the first one left off.

Why it matters for your business

For small projects, one full-stack developer or a small studio can be faster and cheaper than coordinating several specialists, and you have one person accountable for the whole thing. The risk is concentration: if that one person leaves and nothing is documented, nobody else understands the system. Ask for documentation, access to the code repository and every account in your own name from the start, so the work can be handed to someone else if needed.

Common mistakes

• Assuming one full-stack developer can match a specialist in every area on a complex product.
• Letting one person hold every password and the only copy of the code.
• Choosing an unusual stack because the developer likes it, making future hires harder.
• Skipping design because the developer can build the screens, and ending up with a functional but confusing interface.

Questions people ask

Should I hire a full-stack developer or specialists?

For a business website or a modest web app, a full-stack developer or small studio is usually the practical choice. For a large product with heavy traffic, complex interfaces or strict security needs, specialists in front end, back end and infrastructure tend to produce better results.

What is a tech stack?

A tech stack is the combination of technologies a project uses: the front-end language and libraries, the back-end language and framework, the database and the hosting. Knowing your site's stack helps when hiring help, comparing quotes or planning a migration.

Is a full-stack developer also a designer?

Not necessarily. Full stack refers to the technical layers of a build. Some full-stack developers have a good eye for design, but user experience and visual design are separate skills, and many projects benefit from having a designer involved.