Serverless computing: Difference between revisions

Revision as of 07:18, 6 January 2017

Revision as of 15:54, 13 January 2017

Line 2:

'''Serverless computing''', also known as '''Function as a Service (FaaS)''', is a [[cloud computing]] code [[execution (computing)|execution]] model in which the cloud provider fully manages starting and stopping [[virtual machines]] as necessary to serve requests, and requests are billed by an abstract measure of the resources required to satisfy the request, rather than per virtual machine, per hour.<ref name='techcrunch-lambda'>{{cite web|url=https://techcrunch.com/2015/11/24/aws-lamda-makes-serverless-applications-a-reality/|title=AWS Lambda Makes Serverless Applications A Reality|last=Miller|first=Ron|website=[[TechCrunch]]| date=24 Nov 2015|accessdate=10 July 2016}}</ref>

Despite the name, it does not actually involve running code without servers.<ref name='techcrunch-lambda'/> The name "Serverless computing" is so namedused because the business or person that owns the system does not have to purchase, rent or provision servers or virtual machines for the [[Front and back ends|back-end]] code to run on.

Serverless code can be used in conjunction with code written in traditional server style, such as [[microservices]]. For example, part of a [[web application]] could be written as microservices and another part could be written as serverless code. Alternatively, an application could be written that uses no provisioned servers at all, being completely serverless.<ref name='lambda-api-gateway'/>