Serverless Function Triggers in Azure: An Analysis of Latency and Reliability

Examensarbete för masterexamen

Please use this identifier to cite or link to this item:
Download file(s):
File Description SizeFormat 
CSE 22-80 Lagergren Tao.pdfMaster’s thesis in Computer science and engineering5.07 MBAdobe PDFView/Open
Full metadata record
DC FieldValueLanguage
dc.contributor.authorLagergren, Henrik-
dc.contributor.authorTao, Henrik-
dc.contributor.departmentChalmers tekniska högskola / Institutionen för data och informationstekniksv
dc.description.abstractServerless computing has seen a very rapid growth in popularity the recent years, where businesses are now able to completely outsource their IT infrastructure through cloud providers. However, some practitioners that are sensitive to latency and reliability might suffer from unwanted effects when deploying their IT infrastructure to the cloud. This thesis intends to investigate the latency and reliability of various Azure Function triggers offered by Microsoft Azure, one of the most popular cloud providers. In order to conduct such an investigation, a solid benchmark was designed and implemented to test the performance of seven different triggers on two runtimes. The findings, based on the results, from this thesis show that various trigger types have major differences in latency compared to each other. The choice of runtime does also have an impact on latency. However, the impact of the runtime is not as important compared to the choice of trigger type. For bursty workloads, increasing the size of invocation bursts tends to cause longer tail latency for the triggers. The HTTP and Event Hub triggers perform the best, where the shortest and most stable latency was observed for Event Hub on all different burst sizes, while HTTP had some latency increases at the heavier burst sizes. The undoubtedly worst performing trigger was Blob storage. For out-of-order event deliveries, an inter-arrival time of 250ms will lower the risk of high occurrence of out-of-order. To fully ensure ordering, higher invocation delays had to be tested to pinpoint the optimal delay. Missing event deliveries were most apparent for two trigger types, and the other types had too few missing deliveries to draw any conclusions. Duplicate event deliveries were absent for three out of seven trigger types. Results suggest that there might be a difference between runtimes for duplicate deliveries depending on trigger
dc.subjectServerless computingsv
dc.subjectfunction triggerssv
dc.subjectdistributed tracingsv
dc.titleServerless Function Triggers in Azure: An Analysis of Latency and Reliabilitysv
dc.type.degreeExamensarbete för masterexamensv
dc.contributor.examinerBerger, Christian-
dc.contributor.supervisorScheuner, Joel-
Collection:Examensarbeten för masterexamen // Master Theses

Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.