mattiabi
We are not using shared Redis instances. We have our own Redis server implementation, which has a tiered storage model which keeps the hot entries in the memory to better utilize memory usage. Using this we can use smaller instances for the most of the time and migrate the Redis db to a bigger machine in a few seconds when needed.
We are not using Redis OSS, instead we implemented our own Redis server. Because it's not very possible to scale it without increasing the costs and also it would be very challenging to adapt serverless use cases.
Different from the Redis OSS, we are using a tiered storage model which keeps the hot entries in the memory and gradually offloads colder ones. Also we can migrate a Redis DB to a bigger machine in a few seconds when a database needs more resources. We will share more technical information about our architecture in Lambda Store blog.
Since we are not using OSS Redis code, it would be very difficult to adapt it to the serverless model, we cannot support Redis modules directly. But after completing missing Redis commands, we can work on modules support too.
Sure, we are already planning to post blogs about our architecture details. You can follow us on medium: https://medium.com/lambda-store