What you don’t know can’t hurt you. It is difficult to follow this philosophy when work accountability is involved. However, in the software field you can at times close an eye and use a serverless service.
The name can be misleading because serverless computing in truth relies on one or more servers. The term “serverless” describes the experience from the point of view of the client that relies on this type of service that acts as if there were no server.
The serverless cloud computing execution model automatically manages the calculation resources required to run the code of an application. By configuring specific parameters, the user can set up the service so as to independently activate the reshaping of these services only when strictly necessary. For example, when the application users increase in numbers, the infrastructure scales its size to adapt to the new computational needs.
An infrastructure of this kind, differently from other models, such as Infrastructure-as-a-Service, allows you to save costs and calculation resources because they are made available only when used. For this and other reasons, it is an interesting option, but the serverless approach is not the definitive solution. For example, the rules imposed by the service manager could limit the freedom of development of those who manage the application or could reduce the performance.