Private Cloud Platforms comparison & reviews

  • Show Editions
Analysis Summary
Rank
4th 1st 3rd
Score
0%
0%
0%
Extended Analysis Not Enabled Not Enabled Not Enabled
Enquiries Pricing Pricing Pricing
Pros
  • + Strong Storage Capability with Additional Compute and Networking Functionality
  • + Vendor Maturity and Market-share
  • + Simple and Straightforward Editions
  • + True Disconnected Offering of Cloud System
  • + IaaS and PaaS Solution
  • + Enterprise Solution
  • + Mature on-prem IaaS solution
  • + High-fidelity implementation of AWS APIs
  • + Proven at scale over years of operation
Cons
  • - Limited Capability
  • - Few Use Cases
  • - Temporary
  • - Disconnected Mode Only Billed as Capacity
  • - New to Market
  • - Closed Solution
  • - Recent acquisition concerns
  • - No administrative GUI
  • - Missing features beyond API compatability
User Reviews
Details (by section) Expand All Data
expand
Select All
General expand
0%
0%
0%
  Content  
Content Creator
  •  
Overview
  •  
The AWS Snowball Edge is a type of Snowball device with on-board storage and compute power for select AWS capabilities. (see details)
Azure Stack is Microsofts extension of Azure that provides a way to deliver Azure services in an on-premises environment. (see details)
Integrated software stack with AWS-compatible IaaS services.
  Assessment  
Maturity
  •  
Snowball Edge was announced 2016 and builds on AWS which has been around since 2012
Azure Stack was made publicly available June of 2017 and builds off of Azure which has been available since February of 2010
Based on the Eucalyptus code-base that has been in production for over a decade, powering installations beyond 200K cores in size.
Disconnected Offering
  •  
Must connect back to AWS platform for full functionality
Azure Stack can be deployed in disconnected mode
Can be deployed in a disconnected environment
Infrastructure Services expand
0%
0%
0%
  Compute  
Virtual servers
  •  
Virtual servers are called EC2 instances
Azure Stack allows for the deployment of virtual servers called virtual machines
Virtual servers are called cloud instances (equivalent to EC2 instances in AWS)
VM Type - General Purpose
  •  
The SBE1 EC2 instance is the general purpose offering
General purpose VMs are Basic A, Standard A, Av2-series, D-series, DS-series, Dv2-series, DSv2-series
Virtual machine hardware can be configured to take full advantage of the underlying hosts hardware. A collection of instance types can be customized in terms of vCPUs, memory, and disk.
VM Type - Compute Optimized
  •  
The SBE-C EC2 instance is the compute optimized offering
Computed optimized VMs are F-series, Fs-series, Fsv2-series
Compute-optimized instance types can be customized by modifying the instance type
VM Type - Memory Optimized
  •  
There is no memory optimized offering
Memory optimized VMs are D-series, DS-series, Dv2-series, DSv2-series
Memory-optimized instance types can be customized by modifying the instance type
VM Type - Accelerated (GPU)
  •  
The SBE-G EC2 instance is the accelerated GPU offering
There are no accelerated VM offerings with a GPU
GPU instance types can be customized through advanced configuration only. No official documentation.
Metadata URL
  •  
You get access to a subset of metadata typically available to EC2 instances through an internal URL
While Azure has an Instance Metadata service, this functionality is not currently supported on Azure Stack
Metadata URL, featuring EC2-compatible information and thus compatible with cloud-init, is reachable from instances.
Rapid Provisioning
  •  
You can specify the job and resources and Amazon will configure the device for you and ship it out to you
You can easily and quickly deploy virtual machines using the Azure Stack console
System components enable fast provisioning, particularly of EBS-backed instances.
Resize existing VM
  •  
Typically resize an instance using CLI modify-instance-attribute on instanceType attribute but Snowball Edge only allows you to modify userdata
This functionality is supported in Azure Stack as well
EBS-backed instances can be resized after stopping by modifying InstanceType attribute via ModifyInstanceAttribute request (in CLI or Console).
Resource Management
  •  
Resources such as EC2 instances cannot be managed through the console after the device is created and must instead be managed through the CLI/API adding a level of complexity
The Azure Resource Manager provides a platform to manage all resources deployed within the Azure Stack
Resources can be managed from either the Console or CLI/API
Scalability
  •  
A cluster of 5-10 Snowball Edges can be created to offer increased durability and locally scale up or down storage on demand
Azure Stack includes scale sets which allow for automatic scaling of instances based on load
AWS AutoScaling APIs are supported, with performance-based triggers for up- and down-scaling.
VM Imaging
  •  
No mention in the developer guide
You can create and publish a custom marketplace item
Images (akin to AMIs and AKIs) can be created and shared with other cloud users. Existing instances can be saved into an image.
VM Import/Export
  •  
No mention in the developer guide
You can import and export a disk used by a VM. In addition, you may be able to import/export a VM state but this is not confirmed (see details)
Instances can be imported using raw disk or VHD formats. Exports done manually at hypervisor level. No API support for the operation exists.
VM live migration
  •  
AWS does not support live VM migration and as such we shouldnt expect Snowball Edge to do this
Azure Stack supports live VM migration as a preventative measure to protect resources from failing hardware
VMs can be live-migrated using CLI / API. In the event of a host failure instances to not automatically restart.
VM to host affinity
  •  
When deploying a cluster, you can select which nodes an instance runs on
This capability is not supported by Azure Stack
Not supported. Can only be achieved by backend administration using instance migration.
VM to host anti-affinity
  •  
When deploying a cluster, you can select which nodes an instance runs on thus also choosing which nodes it does not run on
Azure Stack provides Availability Sets which replicate the VM across different hosts for high availability thus enforcing host anti-affinity
Not supported. Can only be achieved by backend administration using instance migration.
  Networking  
Cloud virtual networking
  •  
The EC2 instances can have virtual network interfaces attached to them which allows them to communicate with each other and outside devices
The Network Resource Provider delivers a series of Software Defined Networking (SDN) and Network Function Virtualization (NFV) features
Overlays a virtual network on top of your existing network. Supports EDGE (EC2 Classic) and VPCMIDO (AWS VPC) modes.
Cross-premises connectivity
  •  
The Snowball Edge connects into the datacenter and allows for transfer of data between the datacenter and AWS albeit in a slow snail-mail fashion
Cross-premises connectivity can be established in Azure Stacks which are deployed in the connected mode
Support for AWS VPN Gateway is available but only when using VPCMIDO network mode.
DNS hostname resolution
  •  
No mention in the developer guide
Azure Stack supports DNS hostname resolution
DNS names for VM instances is supported automatically
DNS zone management
  •  
No mention in the developer guide
Azure Stack supports the creation and management of DNS zones and records using both the console and the API
No mention in the documentation
IP reassignment
  •  
You can delete the virtual network interface attached to an EC2 instance and then create a new virtual network interface for that EC2 instance with a new static IP address
You can reassign an IP by modifying the virtual network interface or by deleting it and creating a new one (Experience)
Elastic IP and Elastic Network Interface functionality enables flexible IP address assignment.
Load balancing
  •  
No mention in the developer guide
The Azure Stack provides load balancing functionality
Elastic Load Balancer is an included service.
Network Interfaces
  •  
The device has a set of external network interfaces for connectivity into the customer datacenter (see details)
You can create and modify network interfaces attached to virtual machines (Experience)
Elastic Network Interface functionality allows attaching and detaching of virtual NICs to instances
Outbound Network Connectivity
  •  
The device has a set of external network interfaces for connectivity into the customer datacenter (see details)
The Azure Stack is integrated into the customers datacenter and has outbound network connectivity to the customers border
Can be configured to connect to external networks with both EDGE (EC2 Classic) and VPCMIDO (Amazon VPC) networking modes.
Public IP Address
  •  
Can attach a virtual network interface to your EC2 instance and specify a public IP address for use
Azure Stack supports IPv4 public addresses
Public IP addresses can be assigned to instances either automatically or from a pool of Elastic IP addresses.
SR-IOV support
  •  
No mention in the developer guide
No mention of this capability for Azure Stack
Can be customized to use SR-IOV for instance networking by advanced configuration only. No official documentation.
VM Security Groups
  •  
Security groups exist and can be configured for EC2 instances similar to the way they work in AWS with limitations
VM Security groups are provided as network security groups
Instances can be added to a security group which has a specific network security policy applied to it.
Virtual Network Peering
  •  
Virtual Private Clouds (VPCs) are not supported in Snowball Edge and thus you cannot make virtual networks to peer
Not supported as of 20190124
Ability to create a peering connection between two VPCs is supported.
  Storage  
Object storage
  •  
The Snowball Edge supports S3 (object storage) as its primary purpose is downloading customer data from a remote datacenter which can then later be transferred to S3 in AWS
Azure Stack provides blob storage for object storage
Supports S3-compatible object storage using its Object Storage Gateway (OSG)
Block storage
  •  
Block storage must exist as the Snowball Edge is capable of hosting EC2 instances but end-users have no access to block storage and cannot attach volumes themselves to EC2 instances
Azure Stack supports page blobs which are the equivalent of block storage
Elastic Block Storage (EBS) provides block-level storage volumes that you can attach to instances.
Shared file storage
  •  
Once connected to the datacenter, the S3 Adapter for Snowball or NFS mount point can be used to upload data from the datacenter into the Snowball Edge
Azure Stack does not provide a SMB or NFS solution
Shared file storage is not supported.
Backup
  •  
By its nature, the device offers data backup for data stored within a datacenter albeit in a slower process
Microsoft Azure Backup Server can be used to back up data within Azure Stack (see details)
Procedures for backing up and restoring everything except root disks of instance-store (ephemeral) instances are documented.
Local Data Protection
  •  
The Snowball Edge employs defense-in-depth for data protection including a ruggedized tamper-reistant enclosure, 256-bit encrpytion, and a TPM
Local data is encrypted and replicated across nodes in case of hardware failure
Relies on replication features of underlying software and hardware (RAID and Ceph) for local data protection from hardware failures.
Remote Replication
  •  
By its nature, the device offers remote replication for data stored within a datacenter albeit in a slower process
The only replication option available is locally redundant storage
No special functionality for automatic remote replication are provided, but backup process can include transfer of backed up data offsite for disaster recovery.
Snapshots
  •  
No mention in the developer guide
Snapshots are supported for blobs (limited to 1000 per blob) but not for page blobs
EBS snapshots are supported in both Web console and via CLI/API.
Storage Architecture
  •  
Each Snowball Edge node provides betwee 42TB and 80TB (see details)
Azure Stack provides for either a hybrid or all-flash storage architechture
Deployed as customer configurable two-level storage system. Support for HCI not documented.
Storage QoS
  •  
No mention in the developer guide
Azure Stack supports standard and premium storage
Supports only a single storage class for both block and object storage.
Storage Scalability
  •  
Multiple Snowball Edges can be clustered to increase data durability as well as locally grow and shrink storage on demand
Azure Stack operators can increase the overall capacity of an existing scale unit by adding additional scale unit nodes
The Storage Controller (SC) and Object Storage Gateway (OSG) are molular and enable storage capacity to be dynamically allocated independent of the system.
Platform Services expand
0%
0%
0%
  Compute  
Kubernetes Orchestration
  •  
No mention in the developer guide
Azure Stack has a preview capability to deploy a Kubernetes cluster but it is not supported in the disconnected scenario
No support for Kubernetes orchestration is available.
Serverless
  •  
The Snowball Edge offers access to AWS Lambda which can execute serverless functions based on S3 storage actions made on the device
App Service (available in PaaS offering) provides Azure Functions which executes event-driven serverless workloads
No support for a serverless runtime is available.
  Data  
Relational database
  •  
No mention in the developer guide
Relational databases are supported through the use of optional resource providers SQL Server and MySQL Server
No support for DBaaS is available.
NoSQL—key/value storage
  •  
No mention in the developer guide
Table storage is Microsofts NoSQL key/attribute store
No support for a NoSQL database is available.
Caching
  •  
No mention in the developer guide
No mention of Azure Cache for Redis being available but can use Redis marketplace item
No support for an in-memory cache service is available.
  Developer Tools  
Message Queuing
  •  
No mention in the developer guide
Queue storage provides the capability for message queuing
No support for message queuing is available.