Benutzer:Stp/private infrastructure/provider comparison

General -> good things, great features -> criticism -> pricing -> good or not for our infrastructure? (layout for each fulltext)

Rackspace

Rackspace as the founder of the openstack initiative has a great relationship to opensource communities, which is providing customers with more choices and ease to switch providers. The usual virtual machines and block storage (ssd or disk) are provided. Furthermore a wide range of other services (mysql, loadbalancers, object storage, etc.) are offered. The object storage with the ability to use Akamai as CDN and additional features (expiring objects, static site hosting, etc.) is something to consider for public objects. Hosting with Rackspace provides you with a lot of choices, backed by opensource projects. Switching providers is made easier compared to others. The hosting location and Rackspace being an US company raises privacy concerns.
Rackspace is providing dedicated servers and the ability to connect them to virtual machines to provide a hybrid hosting solution, but one of the key components for the "private infrastructure" is data privacy and therefore Rackspace is not usable for the planned infrastructure.
(Virtual machines, block storage and object storage are considered for cloud-bursting of public data)

Amazon Webservices

AWS is the biggest cloud provider in the market. Key products include virtual machines (EC2), block storage (EBS) and object storage (S3). AWS gives you a great amount of additional services (mysql, nosql, loadbalancer, etc.). Using these gives the possibility to develop less and strengthen your key ideas(code).
The downside of using AWS, especially the additional services, is lock-in. It is not easy to switch providers if you need to. Another downside is the server location and US company status.
Building projects/services on-top of AWS is great, but considering no dedicated servers, the lock-in problem and the privacy issues, AWS is not usable for the planned infrastructure.
(No consideration for cloud-bursting weighting the closed infrastructure)

Google Compute Engine

Google Compute Engine is providing virtual machines on a massive scale to customers. With products such as object storage (Cloud Storage) and services for crunching massive amounts of data. Google has entered the market late, but is providing a great deal of products. It is designed for more specialized workloads (data crunching, batch-processing etc.) and not as general purpose as AWS and Rackspace. As with AWS, Google is using a closed system and lock-in problems can arise, furthermore no dedicated servers can be provided.<br\> (No consideration for cloud-bursting weighting the closed infrastructure)

Noris

Noris is providing datacenter services to subcompanies (providing colocation). They sell shared hosting and virtual machines, therefore they were dismissed, after the decision for not using colocation was made.
(Mainlab could not be considered for cloud-bursting, because of missing api compatibility to scalr)

mainlab.de

Mainlab is providing virtual machines and colocation through (rackbase.de) to their costumers. TODO: additional information.
(Mainlab could not be considered for cloud-bursting, because of missing api compatibility to scalr)

interxion.com

Interxion.com has a wide range of server housing locations and is considered a great place for multi datacenter colocation solutions. Data privacy depends on the chosen datacenter location. Be careful. Interxion was dismissed from the list of considered providers, after the decision for not using colocation was made.

datacenter.de

Datacenter.de was dismissed from the list of considered providers, after the decision for not using colocation was made. No detailed information was dug up, as the provider was only supplying colocation and virtual machines.
(Datacenter.de could not be considered for cloud-bursting, because of missing api compatibility to scalr)

Vollmar.net

[TODO: critism about providers] [TODO: price aspects -> price winner] [TODO: feature pricing ...hetzner] [TODO: additional features available/ease of use relevant to project] [TODO: summary which provider was choosen and why in the end]