Skip to content

01_TheCaseForLambda.md

Latest commit

 

History

History
38 lines (27 loc) · 2.32 KB

01_TheCaseForLambda.md

File metadata and controls

38 lines (27 loc) · 2.32 KB

The case for QuantumMaid + AWS Lambda

Why AWS Lambda?

AWS Lambda has been a big deal since it was introduced back in 2014. With Lamba, there is no need to provision stateful servers such as Docker containers or virtual machine instances. These incur hourly charges whether they serve requests or not.

Lambda only incurs charges when requests are served, if at all.

The AWS Free Tier is relatively generous:

  • The first monthly 1.000.000 requests and 400.000 GB-seconds in AWS Lambda are free forever.
  • The first 5 GB of storage in AWS S3 are free for the first 12 months following your AWS account creation.

So this tutorial will most likely cost you nothing if you're a new or casual AWS user. Be sure, however, to not skip the final cleanup section when you're done with this tutorial.

Why QuantumMaid + AWS Lambda?

The Lambda function created in this tutorial contains very little user code. Its execution mostly gauges QuantumMaid libraries' initialization and invocation overhead.

This, in turn, allows the QuantumMaid team to run automated tests on it whenever new versions are released. Regressions on size and performance characteristics are therefore caught and remediated early.

This means that QuantumMaid users can rely on those characteristics, knowing that they will hold true, or even improve, but not regress, in future. At present, the following holds true for the Lambda function we'll create in this tutorial:

  • It has a code size of less than 1.4 M ( source)
  • Its first (cold) invocation duration is less than 2.5 s ( source)
  • From the second invocation onwards, the invocation duration is less than 30 ms ( source) Next, we'll create the basic function.

Overview   →