AWS OpsWorks vs. Spinnaker

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
AWS OpsWorks
Score 4.6 out of 10
N/A
AWS OpsWorks is a configuration management service that provides managed instances of Chef and Puppet.N/A
Spinnaker
Score 7.9 out of 10
N/A
Spinnaker is an open source continuous delivery platform with a range of cluster management and deployment management features, originally developed at Netflix.N/A
Pricing
AWS OpsWorksSpinnaker
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
AWS OpsWorksSpinnaker
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details——
More Pricing Information
Best Alternatives
AWS OpsWorksSpinnaker
Small Businesses
HashiCorp Terraform
HashiCorp Terraform
Score 8.6 out of 10
GitLab
GitLab
Score 8.9 out of 10
Medium-sized Companies
Ansible
Ansible
Score 9.0 out of 10
AWS CodePipeline
AWS CodePipeline
Score 9.2 out of 10
Enterprises
Ansible
Ansible
Score 9.0 out of 10
AWS CodePipeline
AWS CodePipeline
Score 9.2 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
AWS OpsWorksSpinnaker
Likelihood to Recommend
6.0
(3 ratings)
7.0
(3 ratings)
Support Rating
6.0
(1 ratings)
-
(0 ratings)
User Testimonials
AWS OpsWorksSpinnaker
Likelihood to Recommend
Amazon AWS
Where you already have some Chef recipes to build your application boxes and are happy to run directly on VMs, OpsWorks really shines. It won't do anything too complex for you, so it only really works well for simple stacks (load balancers, application layers, database layers). If you want to do more complex infrastructure, Cloudformation or Terraform are probably worth looking at.
Read full review
Netflix
Spinnaker suits well for applications which are stateless and can adapt to an immutable architecture of deployment. But for applications which are stateful and cannot afford to spin up new servers for every deployment doesn't go well with Spinnaker. It can handle only deployments which are VM based and cannot support deployments to serverless architecture like AWS Lambda etc.
Read full review
Pros
Amazon AWS
  • connect between serveral AWS services (EC2, RDS, ELB)
  • easy configuration management deployment via Chef
Read full review
Netflix
  • Fast deployments.
  • Can be integrated with a good variety of other products.
  • Also provides some insights from your environment.
Read full review
Cons
Amazon AWS
  • Getting up and running with OpsWorks is a very technical and potentially time-consuming process. You need to know the ins and outs of Chef/Puppet if you really want to get into it and there isn't a convenient way to test out the environment locally so debugging can be time-consuming.
  • To take advantage of some of the newer AWS instance types you need to be running on a VPC, which again is a pain if you don't have a DevOps team.
  • The error logs and monitoring metrics in OpsWorks are pretty basic and haven't changed much over the years.
Read full review
Netflix
  • It does NOT support CFN based deployments
  • Windows based systems finds it difficult to onboard to Spinnaker.
  • Pipeline level access authorisation is not there.
  • Support for EBS volume encryption is probably missing.
  • Attach/detach EBS volumes during deployments is difficult.
  • No support to deploy the artifacts without re-creating the servers. Only pure immutable deployment are allowed.
  • Open-source - so good and bad!
  • Spinnaker on its own has 10 underlying micro services. Managing Spinnaker needs a focussed platform approach.
  • User authentication is easy but authorisation management is not straight forward.
Read full review
Support Rating
Amazon AWS
Unless you pay for a pricey support package getting support on OpsWorks will be pretty slow. Documentation is also relatively limited and sometimes hard to follow when compared to competitors. Generally, we've been able to get the answers we need from OpsWorks support when we run into problems but don't expect rapid responses.
Read full review
Netflix
No answers on this topic
Alternatives Considered
Amazon AWS
OpsWorks isn't really a direct competitor to Terraform/Cloudformation, but it does allow you to do some of the more simple things on offer quite quickly and effectively. Opsworks was used for this reason, along with existing internal knowledge of Chef. Along with some of the other services on offer from AWS, it is good to use as a stepping stone along the way when building your systems - or perhaps it would be entirely suitable for a fairly simple project.
Read full review
Netflix
• Pipeline Expressiveness • Self-Service/Override • Visibility of Client Teams • Operability of Client Teams - • High-Quality Integrations (AWS, IHP, Google) • Extensibility – (Ability to add code) • The maturity of Deployment Process • Speed/Ease of Onboarding
Read full review
Return on Investment
Amazon AWS
  • very quick way of creating new infrastructure
  • low maintenance costs
  • easy to create high availability setups thus reducing costs
Read full review
Netflix
  • By using Spinnaker we are able to deploy new versions of our product quickly.
  • A deployment takes in average 2 minutes.
  • Our investment on Spinnaker was just time learning it.
Read full review
ScreenShots