SC or Dedicated?

 

This is articles concerning the application and capabilities of the virtual platform we offer, our first cloud’ platform that is true.

The platforms you can expect can be generalized into three families:

– Shared;

– Virtual;

– Dedicated.

… and sure, this is an exceptionally broad brush I am using.

rackspace colocation

To start out this whol story – you need a beginning:

Once upon a right time the progression was quite simple. Shared enviroment, virtual machine, devoted host, high availability group of servers, geographic balancing. Easy life.

This is a pattern of progression that existed in a world where servers would draw an amp or more each, and you would run out of power in a rack way … WAY before you ran out of space.

These days, the relative lines are blurred, and with servers being more likely to be drawing a 3rd of an amp for significantly more performance, the progression has changed.

It can pretty much be narrowed down to your following statements:

“Shared – one size fits all – economical delivery.“

“You want full control of the configuration – you need dedicated or VM.“

“If you require LARGE quantities of storage – you will need dedicated.“

You need virtual.“If you need small, robust and resilient deployments –“

Sure – it is possible to build the rackspace colocation of the dreams (for an amount tag to fit and a commitment) – as well as in which case you are able to be as fast as you like – but utilizing the current trend for self-contained little deployments – almost containerized or devices – then suddenly a VM makes all the sense.

The key to the new VM platform is the ability to distribute copies of the file system across multiple locations. While processing will ideally be local to among the copies, it need not be.

The interconnects causeing this to be possible are typical at 10 Gigabit Ethernet – outstripping the write performance of the collective drives, and further reducing the latency.

Files system and processing can (usually) be hot meaning that is migrated you not merely have the resilience of data* – but also of processing power.

* In the way that is same RAID is not a replacement for a good backup strategy – neither is a remotely replicated drive. We offer a daily snapshot (where possible) for the VM platform allowing complete point in time recovery of the entire instance. But should you require a more granular recovery, or have compliance needs – we would recommend the deployment of an R1 solution.

With current processors that are hugely capable and blazing fast RAM – our benchmarks and experiences demonstrate that these are really, VERY competent performers – when contrasted against both our previous VM offerings, and our entry level budget dedicated servers.

In a nutshell: As current trends come full circle back once again to small, agile, fast deployments for servers (without the world of all the various SCSI cabling!) – If you are thinking of smaller deployments in the 50 to 150G array of storage – unless a really specific architecture is a driver – i might without question suggest our rackspace colocation platform and a Windows or Linux VM.