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.

FabioP

PradeepC

Hi PradeepC, I think your proposal is truly excellent and indispensable.

+1 for me.

Adam

Hi @Adam and @Aliysa_Enhance , is there any news regarding the possibility that Enhance Control Panel can have a Server Role dedicated exclusively to Cache (Redis)?

Thank you very much in advance for your support and I look forward to your response, thank you.

FabioP

+1 For me, for this request:

- 1 - Persistent OLS (OpenLiteSpeed) configuration;
Vote this request here: FabioP
- 2 - Redis as a standalone service on a server;
Vote this request here: PradeepC
- 3 - Configure OPcache (opcache.ini) exactly as you can already configure PHP directives (php.ini);
Vote this request here: FabioP
- 4 - Load balancer support;
Vote this request here: Ibuocloud
- 5 - Integration and support with CSF (ConfigServer Security and Firewall);
Vote this request here: FabioP
- 6 - Integration and support with CXS (ConfigServer eXploit Scanner);
Vote this request here: FabioP
- 7 - Integration and support with Immunify 360;
Vote this request here: webjive

Greetings and have a nice day.

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!

xyzulu

I'm not against this idea.. but do you know how easy it is to setup redis on a server (even an enhance one)? What advantages would having this as an Enhance option for a server in your cluster really give you?

FabioP

xyzulu

Hi xyzulu, yes I know too that it is very easy to install Redis yourself even on the Enhance Control Panel.

Just to list a few advantages, for example, that of being able to create a new Server on Enhance Control Panel and automatically move all the content from the old server to the new one, just to say one of the many advantages, as well as having a much more homogeneous system that can take advantage of the current Enhance Control Panel capabilities and that can also in the future take advantage of all the capabilities that the Enhance Control Panel will surely add from time to time.

gozen

Doesn't that raise a security concern? (have Redis on a different machine? )

xyzulu

gozen Doesn't that raise a security concern? (have Redis on a different machine? )

It depends how the firewall is configured. Aside from security, it could also lead to performance degradation. I'm really not sure the people requesting this feature understand what they are asking for.. or even why.

FabioP

gozen

Hi Gozen, as regards security, I can confirm that having Redis installed on a server specifically dedicated only for Redis does not cause any type of problem (many do it easily) as long as the server hosting it is appropriately configured with all the necessary security practices (and this rule applies in general to anything you intend to host on a server) and on Google there are many very interesting guides about it.

xyzulu

Hi xyzulu, yes, it is true that unfortunately there are many people who don't know what they are doing but fortunately there are always just as many who know what they are doing. Having said that, I don't agree with you regarding the performance degradation if you decide to host Redis on a server dedicated only to Redis and let me explain better:

I personally have always used and still use Redis on a server specifically dedicated only to Redis and I have no degradation in terms of delay and/or latency simply because to avoid this type of problem I host all my services on servers each dedicated to a specific task.

Therefore 1 Server Dedicated to the Web Servers (OpenLiteSpeed) + 1 Server Dedicated to the Databases (MariaDB) + 1 Server Dedicated to the Cache (Redis) + 2 Servers Dedicated to the DNS + 1 Server Dedicated to the Backups + 1 Server Dedicated to the Email Service etc., etc. and obviously I host them all in the same Data Center and all within the same network (indeed to be precise, I host them in the same room of the same Data Center on the same network) and this allows me not to degrade performance in any way in terms of delay and/or latency with the advantage of being able to scale very quickly at the hardware level based on the specific needs of the services on the specific Dedicated Servers that require more resources and this with the Enhance Control Panel, today, is even easier to achieve, thus having the advantage of a scalability much closer to the vertical one than the horizontal one to which we have unfortunately been accustomed for decades with all the problems that derive from it.

Then, as you say, if you find a person who doesn't know what they are doing (and unfortunately there are many around) and hosts the Server Dedicated to the Web Server (NGINX) in China, the Server dedicated to the Databases ( MySQL) in Spain and the Dedicated Cache Server (Redis) in Mexico etc., etc., then the services degrade due to latency times.

So as you can see, anything can be done, you simply need to know how to do it and always know what you are doing.

FabioP

FabioP FabioP

xyzulu I have to self-correct, I meant that horizontal scalability is much better than vertical scalability, that's all.

xyzulu

I understand your point of view. I just don't think giving users with less knowledge or experience than you the ability to create a redis standalone server is good value for money.

FabioP

xyzulu

Hi xyzulu, I also understand your point of view but I don't share it because everything always depends on the target you are referring to.

If as a target we are referring to a user who manages his 4 or 5 low-traffic websites, a simple shared hosting plan will be enough for him and therefore for this target user it makes no sense to talk about NGINX vs OpenLiteSpeed or MySQL vs MariaDB or Redis vs Memcached etc., etc., this type of user only needs a point-and-click system like Windows, let alone if you can talk to them about Linux.

If, however, we are talking about medium and/or medium-large Agencies that manage hundreds and hundreds of websites or if we are talking about medium-small and/or medium-sized Companies that sell Shared Hosting Services, VPS etc., etc., then the matter changes and also the closer you get to vertical scalability, the better it is both in terms of costs and reactivity in the services offered.