Try our new research platform with insights from 80,000+ expert users

AWS CodeDeploy vs Microsoft Azure DevOps comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

AWS CodeDeploy
Ranking in Release Automation
4th
Average Rating
8.2
Number of Reviews
8
Ranking in other categories
No ranking in other categories
Microsoft Azure DevOps
Ranking in Release Automation
1st
Average Rating
8.2
Number of Reviews
130
Ranking in other categories
Application Lifecycle Management (ALM) Suites (2nd), Enterprise Agile Planning Tools (1st)
 

Mindshare comparison

As of November 2024, in the Release Automation category, the mindshare of AWS CodeDeploy is 2.3%, down from 5.4% compared to the previous year. The mindshare of Microsoft Azure DevOps is 39.6%, up from 34.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Release Automation
 

Featured Reviews

Antony Kilament Raj - PeerSpot reviewer
Apr 2, 2024
The default settings of AWS CodeDeploy are highly beneficial for my deployment workflows
I monitor our GitHub repository and integrate it with our database using Pipeline. By creating code builds and deployment scripts, I connect them to our EC2 instances for automatic execution upon code pushes. Our setup includes production and development branches, each serving different purposes…
Akshat Prakash - PeerSpot reviewer
Apr 10, 2024
Allows us to deploy code to production without releasing certain features immediately and agile project management capabilities offer resource-leveling
My company has experienced benefits from using it or from recent updates in Azure Pipelines. For instance, we can manage different code versions from the same repository across different environments. We also use feature flags; the code is deployed, but the feature can be made visible to the end user at a later time. Additionally, as part of the deployment, we integrate automated and regression testing, which stops the deployment if testing fails, thus preventing regression bugs. This saves time and increases productivity by reducing the need for manual testing. Lastly, it integrates with the project management aspects, allowing us to link code deployments with project milestones. Azure DevOps supported our shift towards DevOps culture or practices. We shifted to the cloud environment and started migrating from our data centers about eight or nine years back. It has been a long journey. However, we have used Azure DevOps for almost five to six years in every project. We also use automation testing in Azure, so we have an integrated test suite that allows us to perform functional and regression testing effectively via the Azure DevOps system.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The product's initial setup phase is easy."
"You can easily integrate AWS CodeDeploy with multiple services."
"It is very flexible."
"I can integrate it with other AWS services."
"It's just like every other AWS resource I use. It gets the job done."
"I found the default settings of AWS CodeDeploy to be highly beneficial for my deployment workflows. For instance, when deploying a Node.js application, I manually installed the necessary components on my AWS instance, such as the web server required by developers. Then, I created deployment scripts for starting and stopping instances and performing the deployment itself. These scripts were stored alongside my code in GitHub, ensuring they executed seamlessly with the CI/CD pipeline. Since the project wasn't overly complex, I opted for the default settings, which proved to be efficient and straightforward for deployment."
"The product is easy to use."
"AWS CodeDeploy operates on an on-demand basis. This means that you only pay for the exact duration of the deployment process. Whether it takes one minute, two minutes, or even longer, you're only charged for the time it takes to complete the deployment. You're not locked into paying for dedicated servers."
"The most valuable features of Microsoft Azure DevOps are high-level protection. The protection is very important to the customers to prevent eavesdropping. eavesdropping is when a hacker tries to get into the solution. With this solution is it difficult for them to do it."
"The simplicity is very good and the customer experience is also great."
"Microsoft Azure DevOps has been very good for creating pipelines, and all the solutions for creating task management for developers and for the business."
"The solution is easy to implement and easy to use."
"The most valuable feature in automating our build and release processes with Azure DevOps is the scheduling capability."
"I like the tracking and that we can monitor our velocity."
"The most valuable feature is the complete integration between test cases, pipelines, and issue management."
"It is a well-integrated product in terms of the development lifecycle."
 

Cons

"We have faced some issues and bugs along the way when it comes to stability."
"Deployment and stability should be improved."
"Improvements could be made to AWS CodeDeploy in terms of its agent's compatibility across different operating systems. Currently, there are instances where the agent may not work seamlessly with certain integrations, leading to issues with registering protocols on authorized servers."
"I faced some stability issues."
"AWS should provide its own templates in the console so that I don't need to go anywhere else to get the template for AWS CodeDeploy or AWS CodeBuild."
"AWS CodeDeploy doesn't provide multiple plugins like Jenkins, which is a shortcoming where improvements are required."
"The support and those things are lacking compared to others."
"Microsoft Azure DevOps could improve by providing better integration with other tools. It is very easy to integrate with Azure, but when you need to integrate with other solutions, such as Amazon Web Services, is difficult."
"I would like to automate notifications on sprint planning. When we are getting to the end of sprint planning, we would be automatically notified."
"The user management in the solution could improve."
"I would like to see a bit more project tracking."
"The active directory password system needs some improvement because many times the password for the active directory expires before the set time."
"Proper Gantt charting should be a feature that is included because as it is now, we have to create it ourselves."
"Its price can also be reduced. It would be great if they are a little bit more competitive in terms of pricing because many open-source products are currently available in the market."
"A notable improvement would be adding more notifications."
 

Pricing and Cost Advice

"The product's price is normal."
"AWS CodeDeploy has proven to be a cost-effective solution for us, especially considering the benefits we gain from using it. In terms of pricing, AWS is quite affordable, providing excellent value for the features and services it offers."
"Since we are using a dedicated AWS environment, the solution's pricing is fine."
"It is costly."
"The product is free with EC2."
"The pricing of Azure DevOps falls within the average range and it is fixed."
"The price is reasonable for the solution."
"The cost is quite affordable."
"As a Microsoft Partner, you get a discount on the pricing. Licensing costs are around $80 a month for DevOps, but for Azure, it is about $200 a month."
"As the cost structure is per user, I would recommend paying the cost structure based on the amount of data you use rather than the number of users."
"The licensing costs are reasonable."
"The price of this solution is fair."
"I don't know the pricing of DevOps. It would be much cheaper than ALM because ALM came out as a software product initially. Now they are moving into a cloud and subscription model. In that case, Microsoft is coming from Azure and the cloud and DevOps and software as a service, so it would be much cheaper, but the catch would be that they are trying to get money on all the sides, like an operating system, Microsoft Office, or Microsoft Azure DevOps."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
814,763 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
19%
Financial Services Firm
14%
University
9%
Manufacturing Company
8%
Manufacturing Company
13%
Computer Software Company
13%
Financial Services Firm
12%
Government
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What is your experience regarding pricing and costs for AWS CodeDeploy?
Since we are using a dedicated AWS environment, the solution's pricing is fine.
What is your primary use case for AWS CodeDeploy?
I mostly use it for Jenkins. While using Jenkins, I have been using AWS CodeDeploy. We have been doing deployments using EKS and containerized cluster deployments. Mostly on-prem applications only....
Which is better - Jira or Microsoft Azure DevOps?
Jira is a great centralized tool for just about everything, from local team management to keeping track of products and work logs. It is easy to implement and navigate, and it is stable and scalabl...
Which is better - TFS or Azure DevOps?
TFS and Azure DevOps are different in many ways. TFS was designed for admins, and only offers incremental improvements. In addition, TFS seems complicated to use and I don’t think it has a very fri...
What do you like most about Microsoft Azure DevOps?
Valuable features for project management and tracking in Azure DevOps include a portal displaying test results, check-in/check-out activity, and developer/tester productivity.
 

Also Known As

No data available
Azure DevOps, VSTS, Visual Studio Team Services, MS Azure DevOps
 

Overview

 

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
Alaska Airlines, Iberia Airlines, Columbia, Skype
Find out what your peers are saying about AWS CodeDeploy vs. Microsoft Azure DevOps and other solutions. Updated: October 2024.
814,763 professionals have used our research since 2012.