How to implement a service architecture for clients?

Question

PHP

There is a certain web service. On the server side (Ubuntu/PHP/nginx, Mysql), on the client side HTML/CSS/JS. In general, everything is normal. At the moment, all users connect to the same server and use a common database. I would like to try to implement a virtual space for each user, so that everyone has their own database and their own copy of the application server. So that in case of any problems (an error in the database, in the code, when deploying a new version, etc.), not all users are affected. .
I have never done this before, but I assume that it is done using virtualization technologies. The whole problem is that I don’t really understand how the environment for a new user should be created. For example, when registering a new user, you need to deploy a snapshot of the operating system with all installed utilities, is this done somehow automatically or like "Leave your request, you will get access in a couple of days"?
I would like to hear the experience, if any, has anyone implemented a similar architecture?

Answer 1

I'm interested in the same topic, I started digging towards billing systems. And the following chain turns out.
A person on the site fills out a form in which the desired login is entered and the create button is pressed. A user folder is created on the server via ajax using the BILLmanager API from ISP, for example, in which the script is preinstalled. Here, as I was told in ISP support, it is possible to link BILLmanager ISPmanager through tariffs. The LOGIN.mydomain.ru domain is assigned to the created account. The client visits the created site.
As a result, using the billing system API, we can manage payments for the service, load, and tariff.
I haven’t looked in more detail yet, these are just thoughts ... If you manage to implement it, please let me know.