SC or Dedicated?
SC or Dedicated?
This is a write-up concerning the application and capabilities of the virtual platform you can expect, our first true ‘Cloud’ platform.
The platforms you can expect can be generalized into three families:
… and sure, this is an exceptionally broad brush I am making use of.
To start out this whol story – you need a beginning:
Once upon a time the progression was very easy. Shared enviroment, virtual machine, devoted server, high availability cluster of servers, geographic balancing. Simple life.
This is a pattern of development 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 that is… before ran out of room.
Today, the lines are blurred, and with servers being more prone to be drawing a third of an amp for significantly more performance, the progression has changed.
It can pretty much be narrowed down to the statements that are following
“Shared – one size fits all – affordable delivery.“
“You want full control over the configuration – you need dedicated or VM.“
“If you require LARGE amounts of storage – you need dedicated.“
“If you need small, robust and resilient deployments – you need virtual.“
Sure – it is possible to build the rackspace colocation of your dreams (for a cost tag to match and a commitment) – plus in which case it is possible to be as quickly as you like – but because of the trend that is current self-contained small deployments – almost containerized or devices – then suddenly a VM makes all the sense.
The key to our 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 does not have to be.
The interconnects causeing this to be possible are all at 10 Gigabit Ethernet – outstripping the performance that is write of collective drives, and further reducing the latency.
Files system and processing can (usually) be hot migrated meaning that you not just have the resilience of data* – but also of processing power.
* In the same way that 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 rackspace colocation platform allowing complete point in time recovery of the entire instance. But should you might need a more granular recovery, or have compliance needs – we would suggest the deployment of an R1 solution.
With present processors that are hugely capable and blazing fast RAM – our benchmarks and experiences demonstrate that these are extremely, REALLY competent performers – when contrasted against both our early in the day VM offerings, and our entry level budget dedicated servers.
In a nutshell: As current trends come full circle back into small, agile, fast deployments for servers (without the world of all the different SCSI cabling!) – If you are thinking of smaller deployments in the 50 to 150G array of storage – unless a really certain architecture is a driver – I would without question suggest our SSD based Cloud platform and a Windows or Linux VM.