Answer the question
In order to leave comments, you need to log in
Answer the question
In order to leave comments, you need to log in
Somehow everything is divorced from the task. Why duplicate it like that? And what for in general to duplicate bases and web? It is necessary to expand in narrow places, and not all in a crowd!
Usually, a web application consists of at least three components, application (php/python/node/java/go ....), statics (images, videos), databases (mysql/redis/elastic/mongo .... )
All these parts are clustered separately, and usually by different mechanisms.
Moreover, if we have a site for photos, with a bunch of static, then we will probably have to forget about PHP and the database altogether, which will be loaded only with the return of images and their caching. In total, in this case we get one server (or even a virtual machine) with PHP + MySQL, and a bunch of servers with static, a couple of caching servers, and a couple for converting images.
So, I would say, your scheme is about nothing!
it looks like a general scheme has been taken without elaboration, it will work like an average machine on a highly specialized task, if you're lucky - you're not lucky.
About the selection of statics has already been said.
And purely according to the indicated scheme, I would suggest to install a balancer on 10.0.0.2, which distributes the load on all 4 servers.
But in case of errors, it excludes a buggy server from the distribution (i.e. distributes it to 3 servers) and signals to the admin.
And the servers are used more efficiently and the speed is higher for users, and a failed server is excluded in almost the same way as in your scheme
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question