Excited to see the new update! I’m wondering something regarding Redis…
It’s new for me, but I understand that it can be used as a nosql database is this something that can replace my MySQL database?
If yes, is this something on the roadmap to be made easy through Wappler? These things are out of my depth for now 
Not really. It’s not designed for that.
Well you can use Redis indeed as a high performance NoSQL object database.
We are actually making a database connector for it with Server Connect actions to manipulate it.
It isn’t of course full replacement of a normal database, but useful for quick data stores server side.
Thanks for your input, can you give a quick example of something you’d want to put in the quick data stores server side and something that you’d still want to put in a normal database? @George
Session storage and full page cache as already implemented.
Other use cases: leaderboards(reddit, product hunt, etc), rss, job queues, game scores, etc
If you still need relational data you need to use your Mysql DB.
Appreciate it! @JonL Thanks
Hi @George. I have a huge need for this. As I understand it, the work on this functionality has changed the priority and you postponed it until better times?
Please describe in general terms how best to work with Redis from Wappler at the code level at the moment. Small code examples would help me a lot.
My goal is to save a fairly large array of complex data (multi-level arrays) received from a query to the database in a Redis in order to further do various manipulations with this array (filter it, add elements there, remove elements from there, etc.). And send the results of these manipulations to the client already. At the same time, it is necessary to store this data only while the user is working in the application, after which they can be deleted.
I am grateful in advance for your help.
Well initially we thought of just implementing the native Redis commands as server actions.
But still just as with other data structures we need somehow to have the schema defined so we can populate our data pickers.
Defining the schema for each action can be cumbersome so we rather have it defined once in global level.
We are doing this in the upcoming CouchDB support so we might do something similar with Redis.