Serverless computing: Difference between revisions

Revision as of 21:22, 4 August 2016

Revision as of 21:23, 4 August 2016

Line 23:

=== Programming model ===

In serverless computing, the units of code exposed to the outside world are simple [[subroutine|functions]]{{spaced en dash}} for example, in AWS Lambda, they are essentially functions that both consume and produce [[JSON]], although they can make calls to other APIs, and the JSON may be automatically serialized from and deserialized to [[data structure]]s at the option of the programmer. This means that typically, the programmer does not have to worry about [[multithreading (software)|multithreading]] or directly handling [[HTTP]] requests in their code, simplifying the task of back-end software development.estsdhsdsdsdsds

== Disadvantages ==

Line 31:

==== Resource limits ====

Serverless computing is not suited to some computing workloads, such as [[high-performance computing|HPC computing]], because of the resource limits imposed by cloud providers, and also because it would likely be cheaper to bulk-provision the number of servers believed to be required at any given point in time.sdcsdsfsfsfsfsfsfsfsfsfsfs

=== Monitoring and debugging ===