| I started to implement a new idea a few weeks ago, and then I stopped because I wasn’t sure that it’s a good idea. Now I decided to share it with you to see what you think about it. VaporCache, as I named it is an “In-Memory KeyValue Extension” for AWS lambda function. Here are a few things that specifies this: * It’s an AWS Lambda Extension, and it’s only accessible within the lambda execution environment. * It’s in-memory, like any other in-memory database, main storage is memory. * It’s a KeyVakye database, just like Valkey or Redis, and the RESP3 protocol is used here. Meaning you could use any redis client to communicate with it. * It’s not a distributed database. Use cases that I can think of: * To cache data within a lambda execution environment to use it between different invokes.
* To take responsibility for memory management, to prevent OOM errors in lambdas. Looking forward to your feedback. |