In recent years, new tools have evolved that give us alternatives to achieve our work goals. Generally, hosting a software application on the internet implies managing some type of server infrastructure, which means that a virtual or physical server must be managed, along with the operating system and other web server hosting processes.
Traditionally, web applications have been created and implemented in which we have a certain degree of control over the HTTP requests that are sent to a server. Providers (AWS, Azure, or Google Cloud) focus on helping users not worry about configuring infrastructure, allocating resources, and managing them because they are the ones who are in charge of these processes.
The main focus of Serverless is to help us focus on what matters in the web application as the project progresses and to become effective in our work functions. Among its advantages are the facilities it has in infrastructure management, but without forgetting that we must always be active in writing codes, defining events to trigger the actions to be executed, and the services that make the project work, it is necessary to take into account that one of the advantages of serverless is that it allows us to pay for what is consumed, but it is necessary to pay attention to the servers.
In conclusion, normal servers could be replaced by clouds that manage the consumption of resources of the machine, so you can ignore general problems such as configuration, installation of programs, packages, and libraries, and everything you need when you are running an application. Serverless consumes services that are ready and you only focus on the application.