Function as a Service provides developers with a method for implementing serverless computing. For this purpose, a business logic is written within a so-called container, and management is carried out entirely via a readily provided platform. This platform is usually used in the cloud, but the model is also already being used with local and hybrid deployments.
What’s special: FaaS follows a reactive system that is controlled by events. The events are triggered by specific occasions, such as the click on a button, which results in the function being called up. Once the call has been made, the service waits until a new event is generated. The basis for how FaaS works is that the response to the occasion is started and executedstraight away. For example, the upload of an image file can trigger a reaction that results in the file being automatically converted to a specific format.
To execute the responses of the Function as a Service logic, an infrastructure is available at any time, so that permanent server processes aren’t needed in the background. This in turn has a positive effect on scaling options: The cloud provider ensures the availability of the defined functions and provides resource allocation to the second. As a result, when few requests arrive, the application is scaled down. With FaaS, you’re charged only for the resources used – standby times are therefore not incurred.
In practice, two types of applications are particularly well suited for FaaS implementation: infrequently executed workloads and high-volume transactions.