zaghaghi

The idea initiated at my lunch time when we were discussing mushroom foraging in Sweden :-) One funny thing in Sweden is that people keep their mushroom spots secret, they happily give you collected mushrooms but not the location.

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.

It's possible to break the value into smaller chunks, but not the logic. the function that's responsible for processing the value needs all the chunks. So network wise the issue will remain.

How we can have Rust style method definition in Python, and how we can separate class members from class methods.

Does it help us to do better programming? I don't know. But I think it's worth sharing.

I always check pwd, think again, and add a space before rm.