Framework
A framework gives an application a technical structure and shared rules. The tasks it handles depend on the chosen framework.
Build on a shared application structure
A framework is a software structure that provides recurring tasks and conventions for building an application. Depending on its focus, it may organise navigation, components or server request processing. Custom code is integrated into that structure.
In a fictional service portal, new case pages follow the same navigation and presentation structure. The team adds business functions within it. Whether a person may handle a particular case still needs rules appropriate to the application.
A library tends to provide functions for selective use; the distinction is not always sharp. A framework is not finished business software either. Selection depends on actual requirements and the team's ability to maintain the application with it over time.
Sources
Related terms
- Software libraryA software library provides reusable functions or components. An application uses it to solve a particular subtask.
- Software dependencyA software dependency is another software component a program needs. Indirectly introduced packages can also affect operation.
- Node.jsNode.js runs JavaScript outside the browser. The runtime provides technical capabilities; the program supplies the actual business logic.
- 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.
Articles on this topic
Software Development with ASES
Custom software, web and mobile apps