Function as a service

Function as a service (FaaS) is a category of cloud computing services that provides a platform allowing customers to develop, run, and manage application functionalities without the complexity of building and maintaining the infrastructure typically associated with developing and launching an app.[1] Building an application following this model is one way of achieving a "serverless" architecture, and is typically used when building microservices applications.

FaaS was initially offered by various start-ups circa 2010, such as PiCloud.[2]

AWS Lambda[3] was the first FaaS offering by a large public cloud vendor, followed by Google Cloud Functions, Microsoft Azure Functions, IBM/Apache's OpenWhisk (open source) in 2016 and Oracle Cloud Fn (open source) in 2017.

Use cases

Use cases for FaaS are associated with "on-demand" functionality that enables the supporting infrastructure to be powered down and not incurring charges when not in use. Examples include data processing (e.g., batch processing, stream processing, extract-transform-load (ETL)), Internet of things (IoT) services for Internet-connected devices, mobile applications, and web applications.[4]

Comparison with PaaS application hosting services

Platform as a service (PaaS) application hosting services are similar to FaaS in that they also hide "servers" from developers. However, such hosting services typically always have at least one server process running that receives external requests. Scaling is achieved by booting up more server processes, which the developer is typically charged directly for. Consequently, scalability remains visible to the developer.[5]

By contrast, FaaS does not require any server process constantly being run. While an initial request may take longer to be handled than an application hosting platform (up to several seconds[6]), caching may enable subsequent requests to be handled within milliseconds. As developers only pay for function execution time (and no process idle time), lower costs at higher scalability can be achieved (at the cost of latency).

gollark: Even if you could make a black hole here, it would hardly be much use, you can't look inside it or something.
gollark: Sadly, galaxies are quite big and communications can (with current technology) only go at the speed of light.
gollark: And the variables are guesses.
gollark: You said "solar system" before.
gollark: (sorry for kind of interjecting, I was replying to stuff in <#426053961624190986> somewhat late and it was said that that stuff didn't fit there)

See also

References
  1. Fowler, Martin (4 August 2016). "Serverless Architectures". Retrieved 26 January 2018.
  2. "PiCloud Launches Serverless Computing Platform To The Public".
  3. "Release: AWS Lambda on 2014-11-13". Amazon Web Service. Retrieved 26 February 2017.
  4. "AWS Lambda – Serverless Compute - Amazon Web Services". Amazon Web Services, Inc. Retrieved 2018-05-04.
  5. Avram, Abel (25 June 2016). "FaaS, PaaS, and the Benefits of the Serverless Architecture". InfoQ.
  6. "Dealing with cold starts in AWS Lambda".
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.