rackspace colocation


This is a write-up in regards to the application and capabilities of the virtual platform we provide, our first‘Cloud’ platform that is true.

The platforms we offer can be generalized into three families:

– Shared;

– Virtual;

– Dedicated.

… and sure, this is an brush that is exceptionally broad am utilizing.

To begin this story – you need a beginning:

Once upon a time the progression was quite simple. Hosting that is shared, virtual machine, dedicated server, high availability group of servers, geographic balancing. Effortless life.

This was 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 that is… before ran out of room.

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 development has changed.


It can pretty much be narrowed down to your statements that are following

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

“You want full control over the configuration – you require dedicated or VM.“

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

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

Sure – you’ll build the rackspace colocation of the dreams (for an amount tag to fit and a consignment) – plus in which case you’ll be as quickly 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 your VM that is new platform the ability to distribute copies of the file system across multiple locations. While processing will be local to ideally one of many copies, it does not have to be.

The interconnects making this 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 migrated meaning that you not only 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 VM platform allowing complete point in time recovery of the entire instance. Nonetheless should you might need a more granular recovery, or have compliance needs – we would suggest the implementation of an solution that is r1.

With present hugely capable processors, and blazing fast RAM – our benchmarks and experiences show why these are extremely, VERY competent performers – when compared against both our early in the day rackspace colocation, and our basic 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 range of storage – unless an extremely specific architecture is a driver – I would without question recommend our rackspace colocation and a Windows or Linux VM.