The spec cloud group’s research vision on faas and serverless architectures

Erwin Van Eyk, Alexandru Iosup, Simon Seif, Markus Thömmes

Research output: Chapter in Book / Report / Conference proceedingConference contributionAcademicpeer-review

437 Downloads (Pure)

Abstract

Cloud computing enables an entire ecosystem of developing, composing, and providing IT services. An emerging class of cloud-based software architectures, serverless, focuses on providing software architects the ability to execute arbitrary functions with small overhead in server management, as Function-as-a-service (FaaS). However useful, serverless and FaaS suffer from a community problem that faces every emerging technology, which has indeed also hampered cloud computing a decade ago: lack of clear terminology, and scattered vision about the field. In this work, we address this community problem. We clarify the term serverless, by reducing it to cloud functions as programming units, and a model of executing simple and complex (e.g., workflows of) functions with operations managed primarily by the cloud provider. We propose a research vision, where 4 key directions (perspectives) present 17 technical opportunities and challenges.

Original languageEnglish
Title of host publicationWOSC 2017 - Proceedings of the 2nd International Workshop on Serverless Computing, Part of Middleware 2017
PublisherAssociation for Computing Machinery, Inc
Pages1-4
Number of pages4
ISBN (Electronic)9781450354349
DOIs
Publication statusPublished - 11 Dec 2017
Event2nd International Workshop on Serverless Computing, WOSC 2017 - Las Vegas, United States
Duration: 11 Dec 201715 Dec 2017

Conference

Conference2nd International Workshop on Serverless Computing, WOSC 2017
CountryUnited States
CityLas Vegas
Period11/12/1715/12/17

Keywords

  • Cloud computing
  • FaaS
  • Serverless
  • Software architecture
  • Vision

Fingerprint

Dive into the research topics of 'The spec cloud group’s research vision on faas and serverless architectures'. Together they form a unique fingerprint.

Cite this