CloudNX configurations: an economy of scale
As the old saying goes, ‘show, don’t tell’. We could tell you that our new CloudNX platform offers the next generation of flexibility and scalability, but you might be left wondering what makes it so special. The best way to show you is to look at some of the flexible configurations that are possible for any customer, and the ways in which performance can be scaled on demand.
This first example is a fairly modest configuration for a more basic project, like a WordPress/PHP-based site for a small business. Even so, it takes advantage of brand new features that provide concrete benefits. By separating the application server and the database server into two virtual machines, performance is easier to manage. The private network also provides an extra layer of protection between the database and front end applications – guarding customers’ data even if the web server is compromised.
In the next example, the configuration has been expanded to meet the demands of a more advanced project. For example, a small-medium business site with high traffic and a CRM system that allows staff or customers to register and log in. With two or more application servers, the load balancer can kick into effect, sharing the burden to optimise performance and cope with increased traffic. Shared storage is also on hand to ensure that all servers can access application files. As before, the private network protects the database, and works alongside multiple load-balanced servers with shared storage to ensure no single point of failure.
Once you’ve found your ideal configuration, you can adjust its performance and complexity as your needs change. When it comes to scaling your CloudNX and weighing up the various options, it can be useful to think about them in two broad categories: ‘vertical’ and ‘horizontal’.
Scaling your servers vertically means increasing or decreasing the CPUs, RAM or storage on specific VMs that have already been created. This way, you can boost the performance of your existing configuration to handle higher volumes over a specific period. For instance, you might be expecting a temporary spike in visitor numbers due to an upcoming sale or new product launch. Vertical scaling is quick and easy, making it relatively simple to implement at short notice.
Horizontal scaling is a bit more complicated, involving the creation or removal of VMs as multiple servers in your configuration. By scaling horizontally, you can add servers, private networks and load balancing to create a more complex and resilient system. Cloning is a useful feature for quickly duplicating servers to simplify this process, but planning ahead is also recommended to ensure your configuration supports your long-term development needs.
Of course, in practice you’ll be scaling your servers both vertically and horizontally, and the configuration you decide on will be as unique as your project. The bottom line is that CloudNX can always give you the infrastructure you need right now, whatever its size and complexity, with powerful new features and all-inclusive security – all managed easily via your Cloud Panel. Take a look at the Fasthosts website for more information on CloudNX configurations.