Essay Final Submission: Serverless and the Cold Start Problem #1904
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Assignment Proposal
Title
The Cold Start Problem: How container lifecycle influences serverless functions
Names and KTH ID
Deadline
Deadline task 3
Category
Essay
Description
When working with the servless computing model a common problem that developers face is the cold start problem. This occurs when your preferred cloud provider needs to start your runtime container because an inactive function was called. This is highly correlated with the Docker lifecycle because it is entirely based on container startup cost, the cost of keeping a container running, and the trade offs between pausing or killing a running container (i.e Docker lifecycle).