Can your current server be allocated more resources (RAM, CPU, etc.)? This is generally easier to do for virtual machines than for physical servers. For example, two processes both needing a lot of disk I/O can dramatically slow each other down. There is no silver bullet solution for everyone, but we can provide some guidelines that should make it easy to find the right solution for your particular needs.Īs your resource usage increases due to additional site features or an increase in traffic to the site, you may start to see resource contention on the server. What kind of high availability do you require? What response times will your users or your management consider acceptable? Does your site require any “extra” services or applications, outside of a standard LAMP stack? All of these considerations and (of course, expected traffic to the site) will need to be taken into account when designing, building, and maintaining a multiserver hosting environment. Your infrastructure design will vary greatly based on your website’s requirements. There are a number of ways to architect your environment to ensure fast response times to your visitors and allow you the potential to further scale in the future. However, the leap from a single server to a multiserver infrastructure is a large one.
Whether you are beginning to plan for the launch of a large website or managing the growing pains of an existing site, you will quickly come to the point where one server is not enough to handle the traffic to your site, or you need more reliability than a single server can provide. Chapter 7. Infrastructure Design and Planning
0 kommentar(er)
