Well it kinda depends on what resources you already have. For instance if the application uses all the cores on the computer, simply spinning up another instance of the application won't necessarily mean that requests get handled faster because the two applications would be sharing the resources on the server.

The important thing to remember here is that generally it doesn't make much sense to spin up another instance of the application which would end up using the same resources as the first instance (for example if they try to access the same hard drive at the same time, the operating system has to keep switching access to the hard drive between the two applications).

Most multi-server environments use load balancers to automatically distribute requests between physical machines (see the link in JeffO's answer or https://azure.microsoft.com/en-gb/documentation/articles/load-balancer-overview/) so one of the things you have to keep in mind when programming for scalability, is that one client might not always have every request handled by the same server.

Well it kind of depends on what resources you already have. For instance if the application uses all the cores on the computer, simply spinning up another instance of the application won't necessarily mean that requests get handled faster because the two applications would be sharing the resources on the server.

The important thing to remember here is that generally it doesn't make much sense to spin up another instance of the application which would end up using the same resources as the first instance (for example if they try to access the same hard drive at the same time, the operating system has to keep switching access to the hard drive between the two applications).

Most multi-server environments use load balancers to automatically distribute requests between physical machines (see the link in JeffO's answer or https://azure.microsoft.com/en-gb/documentation/articles/load-balancer-overview/) so one of the things you have to keep in mind when programming for scalability, is that one client might not always have every request handled by the same server.

Well it kinda depends on what resources you already have. For instance if the application uses all the cores on the computer, simply spinning up another instance of the application won't necessarily mean that requests get handled faster because the two applications would be sharing the resources on the server. The important thing to remember here is that generally it doesn't make much sense to spin up another instance of the server application which would just end up using the same resource as the first instance at the same time as the first instance (for instance if they try to access the same hard drive at the same time, the operating system has to keep switching access to the hard drive between the two applications or if they end up having to share the same CPU core then once again the operating system will have to share the CPU time between the two applications). Most multi-server environments use load balancers to automatically distribute users between physical machines (see the link in JeffO's answer or https://azure.microsoft.com/en-gb/documentation/articles/load-balancer-overview/)

Well it kinda depends on what resources you already have. For instance if the application uses all the cores on the computer, simply spinning up another instance of the application won't necessarily mean that requests get handled faster because the two applications would be sharing the resources on the server. 

The important thing to remember here is that generally it doesn't make much sense to spin up another instance of the application which would end up using the same resources as the first instance (for example if they try to access the same hard drive at the same time, the operating system has to keep switching access to the hard drive between the two applications). 

Most multi-server environments use load balancers to automatically distribute requests between physical machines (see the link in JeffO's answer or https://azure.microsoft.com/en-gb/documentation/articles/load-balancer-overview/) so one of the things you have to keep in mind when programming for scalability, is that one client might not always have every request handled by the same server.