As we know, a service works well when we don’t notice the mechanism behind the service itself. In IT, these mechanisms are called backend, a term which refers to the part of a website or software that is not run on the display of the user (such as interface graphics for example) but on a server.
Everything that happens before a webpage can be viewed in a browser is part of the backend. Other examples of backend processes are the memorisation or update of information on a database, the encryption of data or the management of file uploading and downloading. The data generated in the backend is then transferred to the frontend and presented to the user.
While some organisations have separate backend and frontend development teams, the division between the two levels is rarely clear cut. Therefore, many developers write code both for backend and frontend. This type of process is known as full-stack development.