We hear you and see a clear demand for this feature.
I want to say that implementing these features requires a lot of investment, and in 2021 Plesk team keeps focusing on the delivery of other improvements (sad, but true).
We will back to the re-evaluation of these features at the beginning of the next year.
Please continue to share your use cases and requirements, and it would really helpful if you point to existing solutions that we can review and check before implementation.
Your feedback is important to us. Thank you, everyone.
AAbarry d supported this idea ·
An error occurred while saving the commentbarry d commented
Thinking about this logically and outloud here.
But is this not any different than adding redundancy for any other product?
I feel like we don't need Plesk to do this. MySQL is the main item here. You generally need a cluster design in place, to add redundancy, and each approach has caveats (performance, accuracy, delay, read/write masters, you choose. each one is a pill to swallow).
So if we are to duplicate the server, let's talk linux for a second.
That is supremely easy, since it's just files, and permissions.
Install plesk on both, sync the folders and files... simple.
Windows IIS is a bit more challenging, due to how bindings are managed. THAT would require code.
The last bit is to have something like nginx sitting in front, to proxy requests via stream over port 80/443 down to your intended ip address.
This would be a huge undertaking for Plesk to achieve.
Your taking a single-node designed service, and elevating it to cloud-level logistics.
I personally will not be waiting for Plesk to achieve such a task, that could take years.