If you are new to the cloud, you might have a question about the type of architecture of your Windows server configuration in the cloud. The answer is that your configuration can look any way that you want it to look.
In the video below, I draw a diagram of a traditional three-layer application configuration that includes web, application and database servers. In the cloud it is very easy to deploy additional servers, as you need them, to your environment. In particular, the Microsoft Web Farm Framework can help you rapidly stand up web servers, replicating all the data over as well as the parameters so that you can immediately begin serving traffic.
As you begin standing up multiple web servers, you will need to set up a Cloud Load Balancer to help route the traffic. This will ensure that one server doesn’t get overburdened with too much web traffic. Furthermore, it is easy to bring on more application servers and create another database server for mirroring. Finally, our recently launched Cloud Networks functionality will allow you to insert isolated networks to enhance the security of your architecture.
Find out more about horizontal and vertical scaling in this post called Code To Scale.
Bringing on additional servers can be helpful if you have a big marketing campaign or to prepare for the holiday season where traffic is expected to be higher than usual. After that high traffic event is over and you begin to see typical traffic patterns, you can scale down to your original configuration so that you no longer have to pay for the additional servers that you brought online.
Check out Tobin’s previous article for the various ways that you can migrate your Windows configuration to the cloud. You can also get more information on Windows in the Rackspace cloud and find out how to move to the cloud in stages.