Patterns for serverless functions (Function-as-a-Service): A multivocal literature review
Tutkimustuotos › › vertaisarvioitu
Yksityiskohdat
| Alkuperäiskieli | Englanti |
|---|---|
| Otsikko | CLOSER 2020 - Proceedings of the 10th International Conference on Cloud Computing and Services Science |
| Toimittajat | Donald Ferguson, Markus Helfert, Claus Pahl |
| Kustantaja | SCITEPRESS |
| Sivut | 181-192 |
| Sivumäärä | 12 |
| Vuosikerta | 1 |
| ISBN (elektroninen) | 9789897584244 |
| DOI - pysyväislinkit | |
| Tila | Julkaistu - 2020 |
| OKM-julkaisutyyppi | A4 Artikkeli konferenssijulkaisussa |
| Tapahtuma | International Conference on Cloud Computing and Services Science - Virtual, Online Kesto: 7 toukokuuta 2020 → 9 toukokuuta 2020 |
Conference
| Conference | International Conference on Cloud Computing and Services Science |
|---|---|
| Kaupunki | Virtual, Online |
| Ajanjakso | 7/05/20 → 9/05/20 |
Tiivistelmä
[Context] Serverless is a recent technology that enables companies to reduce the overhead for provisioning, scaling and in general managing the infrastructure. Companies are increasingly adopting Serverless, by migrating existing applications to this new paradigm. Different practitioners proposed patterns for composing and managing serverless functions. However, some of these patterns offer different solutions to solve the same problem, which makes it hard to select the most suitable solution for each problem. [Goal] In this work, we aim at supporting practitioners in understanding the different patterns, by classifying them and reporting possible benefits and issues. [Method]We adopted a multivocal literature review process, surveying peer-reviewed and grey literature and classifying patterns (common solutions to solve common problems), together with benefits and issues. [Results] Among 24 selected works, we identified 32 patterns that we classified as orchestration, aggregation, event-management, availability, communication, and authorization. [Conclusion] Practitioners proposed a list of fairly consistent patterns, even if a small number of patterns proposed different solutions to similar problems. Some patterns emerged to circumvent some serverless limitations, while others for some classical technical problems (e.g. publisher/subscriber).