145 lines
5.8 KiB
Markdown
145 lines
5.8 KiB
Markdown
file:: [Castro et al. - 2019 - The rise of serverless computing.pdf](file://C:\Users\david\Zotero\/storage/ZXHNQWBQ/Castro et al. - 2019 - The rise of serverless computing.pdf)
|
|
file-path:: file://C:\Users\david\Zotero\/storage/ZXHNQWBQ/Castro et al. - 2019 - The rise of serverless computing.pdf
|
|
|
|
- burden of scaling was left for developers
|
|
ls-type:: annotation
|
|
hl-page:: 1
|
|
hl-color:: blue
|
|
id:: 63e94cfa-ae10-45ad-a344-90bb384c21ea
|
|
- resources that cloud customers allocate and pay for (leasing VMs), and actual resource utilization (CPU, memory, and so on).
|
|
ls-type:: annotation
|
|
hl-page:: 1
|
|
hl-color:: blue
|
|
id:: 63e94d4c-2a9a-4b9f-8187-210a22ada745
|
|
- containers and microservices
|
|
ls-type:: annotation
|
|
hl-page:: 1
|
|
hl-color:: blue
|
|
id:: 63e94d5c-6b81-415b-94f8-c396a2b963ff
|
|
- pay-asyou-go
|
|
ls-type:: annotation
|
|
hl-page:: 1
|
|
hl-color:: blue
|
|
id:: 63e94d6a-52da-416e-adca-662c99691b5f
|
|
- Developers using serverless computing can get cost savings and scalability without needing to havea high level of cloud computing expertise that is time-consuming to acquire
|
|
ls-type:: annotation
|
|
hl-page:: 1
|
|
hl-color:: blue
|
|
id:: 63e94d7c-b72e-4ae0-bcc1-f6b56a4c510e
|
|
- CNCF Serverless Cloud Native Landscape
|
|
ls-type:: annotation
|
|
hl-page:: 1
|
|
hl-color:: blue
|
|
id:: 63e94d98-ff6d-43b4-aa2c-f53538594658
|
|
- vailability, scalability, fault tolerance, over/ underprovisioning of VM resources, managing servers, and other infrastructure issues.
|
|
ls-type:: annotation
|
|
hl-page:: 3
|
|
hl-color:: blue
|
|
id:: 63e94e33-e56a-4d9f-9773-af04579813c4
|
|
- charging for execution tim
|
|
ls-type:: annotation
|
|
hl-page:: 3
|
|
hl-color:: blue
|
|
id:: 63e94e86-9ced-45de-a16a-d14caa5f06a8
|
|
- esource allocation
|
|
ls-type:: annotation
|
|
hl-page:: 3
|
|
hl-color:: blue
|
|
id:: 63e94e89-dd28-43bb-992d-58ce8275fca6
|
|
- Serverless computing can be defined by its name—less thinking (or caring) about servers
|
|
ls-type:: annotation
|
|
hl-page:: 3
|
|
hl-color:: blue
|
|
id:: 63e94ec3-c438-48ef-a3ec-0cdb27418daf
|
|
- Serverless computing is a platform that hides server usage from developers and runs code on-demand automatically scaled and billed only for the time the code is running.
|
|
ls-type:: annotation
|
|
hl-page:: 3
|
|
hl-color:: green
|
|
id:: 63e94ed3-1fc7-4908-a460-f399cbcc2c8e
|
|
- Cost—billed only for what is running (pay-as-you-go).
|
|
ls-type:: annotation
|
|
hl-page:: 3
|
|
hl-color:: green
|
|
id:: 63e94ee6-1554-4876-a965-a4e42af98596
|
|
- Elasticity—scaling from zero to “infinity.
|
|
ls-type:: annotation
|
|
hl-page:: 3
|
|
hl-color:: green
|
|
id:: 63e94eeb-d7c6-473f-8a29-49751ddfb175
|
|
- Developers do not need to write autoscaling policies or define how machinelevel usage (CPU, memory, and so on) translates to application usage.
|
|
ls-type:: annotation
|
|
hl-page:: 3
|
|
hl-color:: blue
|
|
id:: 63e94f10-c6f0-4dfd-9e94-c5cd90a66460
|
|
- Serverless computing today typically favors small, self-contained units of computation to make it easier to manage and scale in the cloud.
|
|
ls-type:: annotation
|
|
hl-page:: 3
|
|
hl-color:: blue
|
|
id:: 63e94f24-3b21-4f75-956e-7096434ce81a
|
|
- however, no equivalent notion of scaling to zero when it comes to state, since a persistent storage layer is needed.
|
|
ls-type:: annotation
|
|
hl-page:: 3
|
|
hl-color:: blue
|
|
id:: 63e94f4b-83e5-4061-9cf7-66c39bd4b96b
|
|
- Function-as-a-Service is a serverless computing platform where the unit of computation is a function that is executed in response to triggers such as events or HTTP requests.
|
|
ls-type:: annotation
|
|
hl-page:: 4
|
|
hl-color:: green
|
|
id:: 63e94fb1-5a3e-4add-a9d2-2f747a2c862b
|
|
- today serverless and FaaS are often used interchangeably as they are close in meaning and FaaS is the most popular type of serverless computing.
|
|
ls-type:: annotation
|
|
hl-page:: 4
|
|
hl-color:: blue
|
|
id:: 63e94fed-a5a2-4c32-a9b3-6e1e925b2828
|
|
- “A serverless solution is one that costs you nothing to run if nobody is using it (excluding data storage).”
|
|
ls-type:: annotation
|
|
hl-page:: 4
|
|
hl-color:: blue
|
|
id:: 63e94fff-a502-4e5f-b3f0-b6ea851dc505
|
|
- . It assumes serverless computing is a subset of cloud computing so auto-scaling is included and developers have no access to servers.
|
|
ls-type:: annotation
|
|
hl-page:: 4
|
|
hl-color:: blue
|
|
id:: 63e951ad-e145-4ed1-8aab-0d44bbd458d7
|
|
- the lack of need to manage servers
|
|
ls-type:: annotation
|
|
hl-page:: 4
|
|
hl-color:: green
|
|
id:: 63e951b8-8638-4afa-81e6-b06edc84cadc
|
|
- [:span]
|
|
ls-type:: annotation
|
|
hl-page:: 4
|
|
hl-color:: green
|
|
id:: 63e95207-f9be-4ef1-9f96-d02103406cbe
|
|
hl-type:: area
|
|
hl-stamp:: 1676235269548
|
|
- Serverless seems to be the natural progression following recent advancements and adoption of VM and container technologies, where each step up the abstraction layers led to more lightweight units of computation in terms of resource consumption, cost, and speed of development and
|
|
ls-type:: annotation
|
|
hl-page:: 4
|
|
hl-color:: blue
|
|
id:: 63e95365-f9ad-4804-8214-32d89ab107d5
|
|
- deployment
|
|
ls-type:: annotation
|
|
hl-page:: 4
|
|
hl-color:: blue
|
|
id:: 63e95372-cafe-4661-a143-5c4e5e53772e
|
|
- The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations
|
|
ls-type:: annotation
|
|
hl-page:: 4
|
|
hl-color:: blue
|
|
id:: 63ea14a8-eea5-4c24-80a7-c0c64243edf0
|
|
- removing user control over hosting to provide simpler scaling and more attractive billing model:
|
|
ls-type:: annotation
|
|
hl-page:: 4
|
|
hl-color:: blue
|
|
id:: 63ea15a0-c27e-4a2a-a442-04e54ab43937
|
|
- only bills for actual usage while hiding the complexity of scaling
|
|
ls-type:: annotation
|
|
hl-page:: 4
|
|
hl-color:: blue
|
|
id:: 63ea15ac-2b1f-475b-903c-9a009455e78a
|
|
- PaaS users that do not need to pay for idle resources and avoid managing auto-scaling rules.
|
|
ls-type:: annotation
|
|
hl-page:: 4
|
|
hl-color:: purple
|
|
id:: 63ea15c0-5353-421c-8f38-8f60e4188895 |