We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

FaaS or not to FaaS?

Formale Metadaten

Titel
FaaS or not to FaaS?
Untertitel
Visible and invisible benefits of the Serverless paradigma
Serientitel
Anzahl der Teile
49
Autor
Lizenz
CC-Namensnennung 4.0 International:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen.
Identifikatoren
Herausgeber
Erscheinungsjahr
Sprache

Inhaltliche Metadaten

Fachgebiet
Genre
Abstract
I’ll draw a complete picture of the total cost of ownership in serverless applications (including visible and invisible costs) and present a decision-making list for determining if and whether to rely on serverless paradigm in your project. I’ll also discuss current challenges adopting serverless When we talk about prices, we often only talk about Lambda costs. In our applications, however, we rarely use only Lambda. Usually we have other building blocks like API Gateway, data sources like SNS, SQS or Kinesis. We also store our data either in S3 or in serverless databases like DynamoDB or recently in Aurora Serverless. All of these AWS services have their own pricing models to look out for. In this talk, we will draw a complete picture of the total cost of ownership in serverless applications and present a decision-making list for determining if and whether to rely on serverless paradigm in your project. In doing so, we look at the cost aspects as well as other aspects such as understanding application lifecycle, software architecture, platform limitations, organizational knowledge and plattform and tooling maturity. We will also discuss current challenges adopting serverless such as lack of high latency ephemeral storage, lack of durable storage, unsufficient network performance and missing security features.