Smart Location

Zaidpadua

It would be good for enhance to automatically move websites to less busy servers, for example if x server is reaching the limit, notify the administrator, and if enhance deems it necessary to automatically move the website to another less busy server, in order to minimize crashes, another feature could be that if a website requires more resources than available, Move that website to another server if it has them, automatically.
Applying rules of moving only within the same group, etc., would serve for redundant hosting and without drops or load peaks.

Isaia-Arknet_PTY_LTD

This option might be suitable if a proxy server is in front, but to move websites from one IP to another is not always good. Also, keep in mind some clients use external DNS, so the hoster can't change A records for some domains.

The idea is good, but a more elaborate implementation needs tu be figured out. 🙂

Zaidpadua

https://community.enhance.com/d/893-proxy-server

Isaia-Arknet_PTY_LTD I already planted it in another post

Zaidpadua

@Adam

paul-bob

It’s a good idea..

Like a vMotion using vLAN on VMware DRS.

ss88us

I believe Adam said when migrating websites at some point in future a proxy server will start so there's zero downtime. Assuming that's the case and that the DNS is managed either via an Integration and/or natively, this can all happen automatically as you suggest.

I think there needs to be a 'moving' limit i.e. move once per 7 days or something because if the server is under heavy load from an attack, I'm thinking that could trigger many 'moves' of websites all because the attack is targeting one website that is coincidentally being automatically moved too.

Adam

ss88us I believe Adam said when migrating websites at some point in future a proxy server will start so there's zero downtime.

Very soon you will be able to proxy requests from the original server to the new server in case the customer is using external DNS and can't update at a specific time.

Automatic migration of websites based on server load is definitely possible, however there are considerations - for example, if the server has high load because of disk contention then moving a large website might make it worse.

Isaia-Arknet_PTY_LTD Automatic moving websites due to server load should be optional, in my opinion.

This will 100% be optional. I would say the majority of Enhance customers would not want this behaviour but I can see why it might be useful.

Isaia-Arknet_PTY_LTD

Automatic moving websites due to server load should be optional, in my opinion.

The reason: I put a website on a server for a particular reason. For example, I have SSD servers and NVME servers, and some are storage servers using HDD. Also, some specific servers are for fast PHP CPUs with high-speed, matching RAM.
Others are average, according to price.

So, moving from any server to another server only because the lower load is not suitable in most scenarios, except if you host all clients with the same package on a server group.

The idea is very good but must be implemented with proper options and needs to consider scenarios.