CODEWITHSUNDEEP
node.jsredissocket.ioscalability
Kristi Jorgji
Kristi Jorgji

Reputation: 1691

Is Redis a single point of failure in this scenario (Redis, Node.JS, Socket.IO) ?

I use Redis because it allows me to scale my applications horizontally (multiple servers). By using it's pub sub features all my servers can communicate with each other without needing to share memory.

So far, cool! We can add more nodejs servers, BUT all this servers subscribe to one single Redis server. So we have the situation in which we have many NodeJs servers communication to just one Redis server, we can serve more clients but still we have one Redis.

From my tests the Redis server uses less resources so can handle more, but still in this design I think is a SPF. What do you think?

What are the best ways to design a scalable system? I know about master/slave Redis but still I am not convinced if it is the best solution.

Upvotes: 2

Views: 2239

Answers (1)

rsp
rsp

Reputation: 111258

Yes, Redis is a single point of failure in what you describe. Not only in a sense that when it is down then your app is down, but also in the sense that if one of your processes remove or corrupt the data then it is lost forever.

What you can do is use multiple Redis servers and have a good backup strategy.

See this tutorial for clustering:

See these tutorials for backups:

Upvotes: 4

Related Questions