Redis as frontend database to postgres

[aquibbaig]

We will have Redis for session management as a cache db because of the fact that it is in-memory and very fast, here it may/may not write out things to postgres, depends upon if we want session data to persist within the postgres db. [subject to discussion]

[ankitjena]

It won't be on the frontend.

[aquibbaig]

Rephrasing: "a frontend database" is meant as a web server front end (here).

[ankitjena]

How would you do that? Why would you do that. Redis will run in the backend.

[aquibbaig]

Okay. Allow me to explain.

[aquibbaig]

Benefits of adding "Redis" to our tech stack:

1. Persistence into a large data store should only facilitate a limited number of joins as your data grows larger. Hence even simple requests such as fetching a user for a session implementation becomes very expensive. Our stack has a lot of data joins and column updation after each iteration of an event is completed by the user. (See docs). For example: A table join can be of Campaign game mode with Users using a foreign-key such as "score" to display Top-scorers in a campaign.

2. As a suggestion, use Redis for in-memory caching where the requests land in to the database only and only if they aren't found on the cache. "Hash-Tables" may offer us O(1) search complexity.

3. I think we are on the same page here, regarding Redis will run in the backend(my statement was misleading to you perhaps). Redis is run on the web-server as a frontend tool(and the web server is the backend itself). The database requests hit Redis first and if not found here, they go to the main data store. You can use the IO writer and distributed lock system to synchronously write your data into the larger database such as PostGres.

4. Regarding implementations, I'm not quite sure and have to see documentations. But here are some articles, if they may help you well and fine:

• Medium
• Stack Overflow
• Slideshare

Please correct me if I am wrong anywhere. That's my perspective about how things can be easier to scale on a longer run. Thanks!

[aquibbaig]

@ankitjena I am open to healthy discussions in this regard. Shoot me up!

[ankitjena]

@aquibbaig I was clarifying that redis is a in mem DB and not a frontend tool. Not against it. Using frontend with Redis was misleading, yes.

[aquibbaig]

@ankitjena We can work on this later after we have set up a basic layout first. This is scalability which can be extended further. What we can do is use Redis pub/sub with our Postgres db, hence adding a for the future label