- Performing I/O in lambda's is expensive
- At times this I/O is unavoidable, for example, querying databases, or secrets or files.
- generally, we'd like to avoid doing unnessecary. if some of this data rarely changes, lets try to reduce how often it is fetched
- lambda containers are kept around and reused in order to reduce start times, so caching things like db connections, secrets is quite common.
- One thing that bothers me, is i see this quite often
- this bothers me, and generally this gets rewritten like this, to abstract it.
- but we can still do better.
- We could write something a lot more elegant using promises.
- what promises are
- so we could rewrite the above as this.
About the Author
Matt Tyler is a software engineer & cloud tragic working @ Mechanical Rock. He helps teams get the most out of their cloud development experience.