Full-stack development
Full-stack development covers frontend and backend work. The term describes scope, not automatically team size or staffing.
Develop a function across application layers
Full-stack development covers work on an application's frontend and backend. The user interface and related server-side functions are considered together. Data access and connections between the parts may also be included depending on the task.
In a fictional address form, drawing a new field is insufficient. Its input must be transmitted, checked on the server, stored and displayed correctly when reopened. Full-stack work can cover that connected path.
The term does not promise that one person masters every specialist task. It also dictates neither a particular programming language nor a shared repository. When commissioning work, specify which parts will actually be implemented and checked, and who handles operations or specialised security issues.
Sources
Related terms
- FrontendThe frontend is an application’s user-facing interface. Helpful browser feedback does not replace authoritative server-side checks.
- BackendThe backend handles an application’s server-side rules and data. It is more than a database or an administration screen.
- Legacy systemAn existing system still in use, with technical and business dependencies accumulated over time.
- Multi-tenancyMulti-tenancy supports separate customer or group scopes in one solution. A tenant is not automatically one person or one database.
- Browser cacheThe browser cache stores suitable HTTP responses for later use. Reuse and revalidation follow the applicable rules.
- Cache invalidationCache invalidation ends reuse of a stored copy under defined rules. The source record remains a separate concern.
Articles on this topic








Software Development with ASES
Custom software, web and mobile apps


