In part one [https://www.clearvector.com/blog/lambda-internals/] of this series,
we discussed the AWS Lambda execution environment. In this post, we focus on the
challenge of persisting in a serverless environment, gaining access to the data
that Lambda functions process, and one possible method in the form of
