|
Ultimately, an operating system is a "super application" that integrates common functions that can be assimilated to any computer system. The serverless model also uses a previous infrastructure but different from a standard server. Technically it makes use of an alternative conception based on FaaS (Functions as a Service). Applications run on this new infrastructure as stateless, ephemeral containers. A concatenation of effects is produced starting from an event, followed by the creation of a stateless container and finally the execution of the application.
This dynamic represents the maximum power of cloud computing and solves part of the problems seen before in the client-server model. This technology does not imply an overcoming of the client-server model. It simply offers some buy email database advantages that today can already be experienced in very popular services such as Lambda AWS , Microsoft Azure or Google Cloud . These infrastructures add a layer of abstraction on top of the service normally provided by the server.
Programmers the development cycle is simplified and allows them to focus on functionality . The events that launch the service are the same as a call to a server. They can be http requests , requests to databases, file uploads, alert management or scheduled events. The transition to microservices running on top of stateless functions To change from an infrastructure with the client-server model to a serverless model , a thorough prior analysis is necessary.
|
|