Abstract

Serverless computing, epitomized by AWS Lambda, has revolutionized application development and deployment by abstracting away server management and offering auto-scalability. AWS Lambda's 15-minute maximum timeout for function execution, however, presents a unique challenge for users aiming to process longer tasks within the serverless framework. In this paper, we dive deep into the execution dynamics of AWS Lambda within the AWS serverless environment, with a particular focus on extended execution times. As serverless computing gains traction, understanding the nuances and limitations of AWS Lambda's default settings becomes paramount.
 This paper investigates different request handling mechanisms within AWS Lambda and presents empirical data to demystify the underlying processes. By addressing the challenges posed by long-running serverless functions, we aim to provide practical insights and potential solutions for developers and architects seeking to optimize their serverless applications. In the quest for efficient triggering mechanisms for extended serverless functions, this paper offers valuable guidance, empowering users to leverage AWS Lambda effectively while circumventing the default timeout constraints.

Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call