Framework
A framework is a ready set of tools, libraries and conventions that imposes a defined structure on an application and provides proven solutions to recurring problems. Instead of building every application from the ground up, the developer uses a foundation prepared by the framework's authors and fills it with their own business logic. This makes work faster, keeps the code more organised, and gives the team a shared way of structuring the project.
How a framework works
A defining trait of a framework is inversion of control: the framework governs the application's main flow and calls the developer's code at the appropriate moments. This sets it apart from an ordinary library, which the programmer calls themselves. A framework usually also imposes an architecture — such as the MVC (Model-View-Controller) pattern — along with naming and file-organisation conventions, which makes the project easier to maintain and grow across many developers.
Types of framework
There are backend frameworks (such as Laravel in PHP, Django in Python, Spring Boot in Java) that handle server logic and the database, and frontend frameworks (React, Vue, Angular) responsible for the interface in the browser. There are also full-stack frameworks that combine both worlds.
Practical applications
Frameworks are used in all kinds of projects — from simple sites to elaborate SaaS platforms. They speed up building an MVP, standardise a team's backend and frontend work, and reduce the risk of security bugs, because they provide ready, tested mechanisms for authentication, validation and protection against common attacks. When deploying, it is worth choosing a hosting environment that matches the given framework's requirements — for example the right PHP version for Laravel.
Powiązane pojęcia
Najczęstsze pytania
How is a framework different from a library?
With a library, the developer calls its functions whenever they need them. A framework works the other way around — it controls the flow of the application and calls the developer's code at the right moments (the inversion-of-control principle). A framework imposes structure, a library merely provides tools.
Is it worth using a framework instead of building everything from scratch?
In most projects, yes. A framework provides tested solutions to common problems — routing, database access, security — so the team can focus on business logic. Building everything yourself only makes sense for very specific, unusual requirements.