Serverless Computing: An Investigation of Deployment Environments for Web APIs
Cloud vendors offer a variety of serverless technologies promising high availability and dynamic scaling while reducing operational and maintenance costs. One such technology, serverless computing, or function-as-a-service (FaaS), is advertised as a good candidate for web applications, data-processi...
| Main Authors: | , , |
|---|---|
| Format: | Article |
| Language: | English |
| Published: |
MDPI AG
2019-06-01
|
| Series: | Computers |
| Subjects: | |
| Online Access: | https://www.mdpi.com/2073-431X/8/2/50 |
| _version_ | 1811187950724055040 |
|---|---|
| author | Cosmina Ivan Radu Vasile Vasile Dadarlat |
| author_facet | Cosmina Ivan Radu Vasile Vasile Dadarlat |
| author_sort | Cosmina Ivan |
| collection | DOAJ |
| description | Cloud vendors offer a variety of serverless technologies promising high availability and dynamic scaling while reducing operational and maintenance costs. One such technology, serverless computing, or function-as-a-service (FaaS), is advertised as a good candidate for web applications, data-processing, or backend services, where you only pay for usage. Unlike virtual machines (VMs), they come with automatic resource provisioning and allocation, providing elastic and automatic scaling. We present the results from our investigation of a specific serverless candidate, Web Application Programming Interface or Web API, deployed on virtual machines and as function(s)-as-a-service. We contrast these deployments by varying the number of concurrent users for measuring response times and costs. We found no significant response time differences between deployments when VMs are configured for the expected load, and test scenarios are within the FaaS hardware limitations. Higher numbers of concurrent users or unexpected user growths are effortlessly handled by FaaS, whereas additional labor must be invested in VMs for equivalent results. We identified that despite the advantages serverless computing brings, there is no clear choice between serverless or virtual machines for a Web API application because one needs to carefully measure costs and factor-in all components that are included with FaaS. |
| first_indexed | 2024-04-11T14:12:21Z |
| format | Article |
| id | doaj.art-32ab9c2971a94a09a22b84a8debb6b90 |
| institution | Directory Open Access Journal |
| issn | 2073-431X |
| language | English |
| last_indexed | 2024-04-11T14:12:21Z |
| publishDate | 2019-06-01 |
| publisher | MDPI AG |
| record_format | Article |
| series | Computers |
| spelling | doaj.art-32ab9c2971a94a09a22b84a8debb6b902022-12-22T04:19:41ZengMDPI AGComputers2073-431X2019-06-01825010.3390/computers8020050computers8020050Serverless Computing: An Investigation of Deployment Environments for Web APIsCosmina Ivan0Radu Vasile1Vasile Dadarlat2Department of Computer Science, Technical University of Cluj-Napoca, 400027 Cluj-Napoca, RomaniaQiagen, 400000 Cluj-Napoca, RomaniaDepartment of Computer Science, Technical University of Cluj-Napoca, 400027 Cluj-Napoca, RomaniaCloud vendors offer a variety of serverless technologies promising high availability and dynamic scaling while reducing operational and maintenance costs. One such technology, serverless computing, or function-as-a-service (FaaS), is advertised as a good candidate for web applications, data-processing, or backend services, where you only pay for usage. Unlike virtual machines (VMs), they come with automatic resource provisioning and allocation, providing elastic and automatic scaling. We present the results from our investigation of a specific serverless candidate, Web Application Programming Interface or Web API, deployed on virtual machines and as function(s)-as-a-service. We contrast these deployments by varying the number of concurrent users for measuring response times and costs. We found no significant response time differences between deployments when VMs are configured for the expected load, and test scenarios are within the FaaS hardware limitations. Higher numbers of concurrent users or unexpected user growths are effortlessly handled by FaaS, whereas additional labor must be invested in VMs for equivalent results. We identified that despite the advantages serverless computing brings, there is no clear choice between serverless or virtual machines for a Web API application because one needs to carefully measure costs and factor-in all components that are included with FaaS.https://www.mdpi.com/2073-431X/8/2/50serverlessFunction-as-a-Serviceresponse timeWeb API |
| spellingShingle | Cosmina Ivan Radu Vasile Vasile Dadarlat Serverless Computing: An Investigation of Deployment Environments for Web APIs Computers serverless Function-as-a-Service response time Web API |
| title | Serverless Computing: An Investigation of Deployment Environments for Web APIs |
| title_full | Serverless Computing: An Investigation of Deployment Environments for Web APIs |
| title_fullStr | Serverless Computing: An Investigation of Deployment Environments for Web APIs |
| title_full_unstemmed | Serverless Computing: An Investigation of Deployment Environments for Web APIs |
| title_short | Serverless Computing: An Investigation of Deployment Environments for Web APIs |
| title_sort | serverless computing an investigation of deployment environments for web apis |
| topic | serverless Function-as-a-Service response time Web API |
| url | https://www.mdpi.com/2073-431X/8/2/50 |
| work_keys_str_mv | AT cosminaivan serverlesscomputinganinvestigationofdeploymentenvironmentsforwebapis AT raduvasile serverlesscomputinganinvestigationofdeploymentenvironmentsforwebapis AT vasiledadarlat serverlesscomputinganinvestigationofdeploymentenvironmentsforwebapis |