Redis on client side

[Miguel Martin]

Hi everyone,

First of all, I´m not asking how to connect from client side (javascript) with Redis.

I´m a newby to Redis, keep this in mind. I´m using redux as the state container/manager. You probably know about it, it is a implementation of the flux pattern where the current state of the app (like snapshots) is kept under  a single place. We´ve evolved our reducers (the way we create new snapshots) to be able to store 5 different types of structures (key-value, key-list, key-set, key-hash, key-ordered-sets), so our business logic modules can use this reducers to store any kind of structure (i think we cover most use cases with this structures). So, then, I start reading about redis and its data structures and I realized they are the same as ours.

So my question is. Redis is an in-memory database. Could it be, somehow, used as a client side in-memory store? .... ok, right now, no, is it? but why? which is the main reason? too much memory usage for a browser? Any other reasons why it can not be adapted?

Thanks a lot for your time and once again, excuse my lack of knowledge of Redis.

[Jan-Erik Rediger]

Redis requires to be run as a server application.
You simply cannot do it in a browser ;)

You can of course provide an API, so your frontend can contact the
backend, which then stores data in Redis.

On Fri, Mar 17, 2017 at 02:47:45AM -0700, Miguel Martin wrote:
> Hi everyone,
>

> First of all, I惴 not asking how to connect from client side (javascript)
> with Redis.
>
> I惴 a newby to Redis, keep this in mind. I惴 using redux as the state

> container/manager. You probably know about it, it is a implementation of
> the flux pattern where the current state of the app (like snapshots) is

> kept under a single place. We扉e evolved our reducers (the way we create

> new snapshots) to be able to store 5 different types of structures
> (key-value, key-list, key-set, key-hash, key-ordered-sets), so our business
> logic modules can use this reducers to store any kind of structure (i think
> we cover most use cases with this structures). So, then, I start reading
> about redis and its data structures and I realized they are the same as
> ours.
>
> So my question is. Redis is an in-memory database. Could it be, somehow,
> used as a client side in-memory store? .... ok, right now, no, is it? but
> why? which is the main reason? too much memory usage for a browser? Any
> other reasons why it can not be adapted?
>
> Thanks a lot for your time and once again, excuse my lack of knowledge of
> Redis.
>

> --
> You received this message because you are subscribed to the Google Groups "Redis DB" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+u...@googlegroups.com.
> To post to this group, send email to redi...@googlegroups.com.
> Visit this group at https://groups.google.com/group/redis-db.
> For more options, visit https://groups.google.com/d/optout.