AWS Vs OpenStack
Here, let’s decode the heights and ranges of 2 of the most discussed cloud technology solutions currently existing. First is the acclaimed Amazon Web Services (AWS), Customers primarily use it for the speed and Advantage of it worldwide cloud hosting capability, and physical infrastructure volumes ie Data Centers; Second is the extremely nifty OpenStack, It serves businesses to set up their proprietary cloud-system based services on standard average hardware.
What is OpenStack
“Large clusters of storage, networking resources, and computation can be managed by an OpenStack system across a data center, which can be administered via a dash console or through an API based on OpenStack. It supports all open source technologies and works well with all popular enterprise software which makes it a perfect solution for diverse infrastructure”
What is AWS
“Amazon Web Services (AWS) is Cloud system offering by the company Amazon, which encompasses all mainstream offerings of a cloud solution such as IaaS (Infrastructure as a Service), PaaS (Platform as a Service) and PaaS (Platform as a Service). Essentially it gives its services via the internet in terms of Bandwidth, Storage and an Ad Hoc support for APIs.
OpenStack – Establishment and Customer Base
OpenStack was launched in 2010, since then its reputation has been continuously growing, and even more after an upgrade in the early half of 2013. There are many business which have been key to the innovations and growth of OpenStack, to name few of many consist of: Arista Networks, Yahoo, Avaya, Canonical, VMware, Citrix, Fujitsu, Cisco, NEC Corp, SUSE Linux, Google, Hewlett-Packard, AT&T, Red Hat , Oracle, Clean Storage, Juniper Networks, Comcast, Solidfire, Intel, Mellanox, International Business Machines, Huawei, VMTurbo, GoDaddy, Ericsson, Dell – EMC, ZTE
Amazon’s selling point is that it partakes a market share among Microsoft, Google, IBM and other players part of Public Cloud ecosystem. OpenStack’s selling point on the other hand is that it is a sustainable substitute to IBM or Alibaba as part of the Private Cloud ecosystem.
The arguments and debates between public cloud model and private cloud is long-familiar and unrelenting. Although the services and technologies are proliferating at a raging speed, to choose between these two platforms across the Scrum – agile processes are still very huge dilemma.
Meanwhile, AWS – Amazon Web Services caters simple slicing, dicing scan the barcode methodology and process, a simple child’s play flow to permit anyone to create cloud products; OpenStack is still very complex at the big picture as it comprises of the below workflow;
- Download & Installation
- Administration & Configuration
- Management and upgradation
Comparison between AWS Vs OpenStack
|Elasticity||Auto Scaling is a part of AWS||Autoscaling wit Heat|
|Virtual servers||based on EC2||Based on Instance in Nova|
|Workflow Service||Follows Simple Workflow Service (SWF)||It has the Mistral – Workflow Service|
|Business Productivity Tools||Amazon WorkDocs||None|
|Workload Management||ELB (Elastic Load Balancer)||Load Balancer as a Service (LBaaS)|
|Billing||AWS Usage and Billing Report||Ceilometer – Telemetry based billing, resource tracking etc|
|Enterprise Messaging:||Simple Queue Service (SQS)||Zaqar, a multi-user cloud messaging service for Mobile and Web|
|Search Service||Elasticsearch Service||Searchlight|
|Alloted Network||DirectConnect||No Dedicated Network|
|Serverless Framework||Lambda||No Serverless Framework|
|SAN Data Storage||EBS(Elastic Block Storage)||Cinder|
|Cache (InMemory)||ElastiCache||No In memory Caching|
|Script project deployment||CodeDeploy Code Commit Code Pipeline||No Application Deployment with Scripts|
|Microservices based Dockers or Containers:||ECS(EC2 Container Service)||Magnum|
|Domain Name System Administration||Route 53||Designate|
|Content delivery Network (CDN)||CloudFront||No Content Distribution Network|
|Templates or Image||AMI(Amazon Machine Image)||Glance|
|Cloud Data Storage Architecture||S3(Simple Storage Service)||Swift|
|Data Warehouse or Database||Redshift||Trove|
|Orchestration or Job Scheduler||AWS Batch||Heat|
|Big Data||EMR (Elastic Map Reduce)||Sahara|
|Identity and Access Management||IAM||KeyStone|
|Collaborated File Sharing||EFS (Elastic File System)||Manila|
|Private Cloud in Public Cloud||VPC (Virtual Private Cloud)||Neutron|
|Managed Hosting Platform||Elastic Beanstalk||There is no Managed Hosting Platform|
|Key/Encryption Management||KMS (Key Management Service)||Barbican|
|Mail Service||Simple Email Service (SES)||There is no Mail Service unless created|
|Speech or Voice recognition||Lex||No Speech or Voice recognition solution|
|Text to Speech Tool||Amazon Polly||No Text to Speech Tool|
|Personal Voice Assistant||Alexa||No Personal Voice Assistant|
|Application development Platforms||Mobile HUB, Mobile SDK, Cognito||No Application development Platforms|
|Machine Learning/NLP||Possible||ML & NLP are not readily available|
|Internet of Things or Connected Smart Systems||AWS IoT||No Internet of Things or Connected Smart Systems:|
|Streaming Analytics or Data||Kinesis||No Streaming Analytics or Data feature|
AWS workflow process, framework, and architecture are mostly owned and entitled to Amazon only, even to its partners such as Eucalyptus or RightScale knew only how to observe and assume the process. Unlike OpenStack, which is a free and open source platform, where if one needs to understand the workflow process, one can basically download the entire code.
So which Platform to use?
Contemporary offerings are given by both cloud computing platforms – OpenStack and AWS; One must decide based on their requirement. With its On-demand usage-based cost model, Amazon Web Services (AWS) will be adequate for longer tenure projects. On the flip side OpenStack’s opensource free license factor is always a game changer.
Below are the use cases for OpenStack over AWS:
- “Grid computing/High-performance Computing is a latent use scenario considering OpenStack, since its ecosystem follows a free source open asset model, and also it supports flexi infrastructure ecosystem.
- “Development/Testing Support: More and more conventional Infrastructure as Service frameworks are with mutual symbiosis to both Quality assurance team and Development team.
- DevOps Best Practices: A development team can use infrastructure as code and the OpenStack Application programming interfaces
- “Measure the product structure to support big data offerings like Apache Spark, Apache Cassandra, and Hadoop.”
- “Parallel to business application hosting: As an alternative to struggling with old school affinities Devote towards the emerging cloud-native apps; This is most emphasized use case of all.