Redis as a standalone service

PradeepC

Hey People,

Currently we have server roles like Application, Database, Email, etc. I would like to propose that we have a server role named "Redis" where on a single server we can host multiple clients who would like to use "Redis".
We already know that "Redis" is RAM intensive, and I think that for smaller clients using the account limits of the plan with "Redis" is fine, but for larger customers, who need a dedicated "Redis" instance, it would be helpful to have a dedicated "Redis" instance.

What are you thoughts on it?

AdamM

PradeepC
Hi
Redis - It is already in the roadmap.

PradeepC

AdamM Is it as a standalone service, where we will need to tick the box to install redis on a machine or is it like on a per website basis which we can switch on or off according to the client requirement and the redis files are already there on the server?

AdamM

PradeepC I don't know exactly how it will work, you should ask the Enhance team.
@Aliysa_Enhance @Adam

Adam

Redis will run within the website's application container. It will therefore be accessible on 127.0.0.1 from the container's perspective. It will be subject to the hard resource limits on the package or any overrides set on the website level.

The ability to use Redis will be a package setting so you can choose to restrict it to dedicated/VPS packages using this functionality.

PradeepC

@Adam It would be beneficial to have it as a standalone service as well with the one you have suggested, where the customers would need it to be decoupled from their plan. We can have packages for Redis as well, with say 512 MB RAM, for $20 a month, 1GB for $40, etc. and sell it to our customers like Kinsta does for $100 a month as you can see here https://kinsta.com/wordpress-hosting/pricing/.

Currently as we assign the Application, Database and Backup server to the website manually or while creating it, we can assign the Redis instance as required.

Adam

Are you talking about a shared redis instance rather than dedicated to the website?

PradeepC

Hello @Adam, Yes, the instance can be both dedicated or shared depending on the requirement.

Dedicated: Dedicated to only one client who has higher requirement but as a separate service.
Shared: Shared between multiple clients/websites but again a separate service.

But according to your plan, if the website is small enough, they can even have it in their container with the limits of the container.

Looking at the forums some are looking at Dedicated Databases where they will only install the Database role and then maybe put few clients or just allocate it for 1 client. Similarly, if the same thing can be achieved for Redis, it would be great!

Adam

I think I understand. So the things you want that are different to current roadmap are:

a) the ability to have redis on a separate server to the php application
b) the ability to have a shared instance of redis for multiple websites

We will consider this as a feature request.

PradeepC

Thanks! Adam

ss88us

PradeepC Redis on a separate server would no doubt cause latency issues, right? Having redis on the same server and/or container as the website would cause a 0ms delay. Just brainstorming here...

prasad0889

ss88us Yes, you are right. Redis will cause some latency when on a different server.
What I understand from @PradeepC's comment is for scaling a bigger website, which has large number of visitors daily it would be better to have it as a separate instance.
Similarly, if the RAM on the container is utilized more my Redis, then webserver and MySQL might give problems.

There are pros and cons to each option here.

PradeepC

prasad0889 Yes, that's exactly what I want to say. If we keep the Redis container in the same DC, the latency can be reduced or in case of AWS or other providers in the same VPC or availability zone, the latency can be reduced.

But yes @prasad0889, having Redis in the same container can cause issues too, where if your base plan has 1GB RAM shared between MySQL, Webserver, etc, then Redis will have some issues too once the memory is full.

Hope to see this soon on the roadmap!