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

AWS Amplify vs Microsoft Azure DevOps comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

AWS Amplify
Ranking in Release Automation
5th
Average Rating
7.4
Reviews Sentiment
7.6
Number of Reviews
7
Ranking in other categories
No ranking in other categories
Microsoft Azure DevOps
Ranking in Release Automation
1st
Average Rating
8.2
Reviews Sentiment
7.1
Number of Reviews
130
Ranking in other categories
Application Lifecycle Management (ALM) Suites (2nd), Enterprise Agile Planning Tools (1st)
 

Mindshare comparison

As of December 2024, in the Release Automation category, the mindshare of AWS Amplify is 2.1%, down from 4.1% compared to the previous year. The mindshare of Microsoft Azure DevOps is 39.5%, up from 35.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Release Automation
 

Featured Reviews

Shrihari Haridas - PeerSpot reviewer
Amplify CLI acts as a single source of truth
The Amplify CLI acts as a single source of truth. You install the SDK from there, and using the Amplify API, you can talk to and manage AWS services directly from your code. You don't need to go to the GUI and click through menus - everything is manageable through the Amplify API at the code level. AWS Amplify integrates seamlessly with other services through AWS CloudFormation. Amplify first connects to the cloud for me. Whenever we write down the SDK, it's managed by CloudFormation. CloudFormation still happens on our cloud for your application because everything is updated with the help of cloud automation. Anything we need to change, we just add it to Amplify, and Amplify triggers the CloudFormation templates. Then it logs permission, updates the whole thing, or whatever you need it to ask.
Akshat Prakash - PeerSpot reviewer
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 link with Figma is very nice. You can create your design in Figma, and then you can import it into AWS Amplify and use it. You can link it to your data source and data bindings."
"The most valuable feature is user management, which includes authentication and authorization."
"The most valuable feature of AWS Amplify is authentication."
"I didn't host my application but have used their backend as a service. It was a complete package with authentication, AWS AppSync, DynamoDB, and GraphQL. AWS Amplify is great if you don't know backend development and don't want to struggle with other backend services like MongoDB. You don't have to worry about what backend language or database to use. If you're confused, enroll with AWS Amplify. I also recommend Google Firebase for similar purposes."
"The only tricky part I experienced was during the initial installation. I followed the documentation, but it wasn't working for some reason. I had to modify some local files in the CLI-generated folder to get it to work. I had to dig deep to find the issue, and it wasn't mentioned in the docs. So, some issues could be better highlighted in the AWS CLI documentation, which would help developers integrate other services more easily. AWS needs to improve its support."
"One of the things I like best about AWS Amplify is its ease of use and strong integration with other AWS services, which enhances efficiency."
"Typically, whenever we make changes and need to switch environments (e.g., dev to production), it's easy for our developers to maintain the state of each environment and make customizations as needed. They don't necessarily need to involve the cloud team for basic management."
"It's a complete solution that has everything you need."
"Great project management feature and Git-based repository."
"The most valuable feature is that we can run integrations with DevOps. From a QA perspective and a testing perspective, we can run those tests and integrate automation tools. Then we can run those tests as part of the deployment process. Every time we are deploying something, it automatically runs all the tests."
"The solution is good for everything, including end-to-end planning and its deployment and testing."
"Azure DevOps is complete and meets all of your expectations. You can develop your own plugins to customize it however you want, so it's highly flexible. We develop personalized plugins or use ones that other programmers create for the Azure Marketplace."
"Azure enables us to create a staging environment through to a production environment in an easier way and then get the code and run that."
"We can eliminate some of the middleman processes."
"Before using this solution, we had to deploy our applications, from pre-production to production, manually."
 

Cons

"AWS can implement multiple web applications, and cross-platform applications, like iOS."
"I like AWS Amplify's documentation. It's comprehensive and includes many examples, so you don't need to ask for help much - you can refer to the docs. It's easy to use. I also appreciate the cost structure. You only pay for what you use. For example, if you use 100 GB, you're charged for that, but if you don't use it, you pay the maintenance cost."
"AWS Amplify could improve in the deployment. It would be beneficial to have more methods, such as automation."
"AWS Amplify can be improved in some areas, particularly in providing more robust documentation and easier customization options."
"I don't think there are major issues, but there is room for improvement in the UI/UX of AWS Amplify. The UI still needs to be more polished and user-friendly. It's currently a bit like drag-and-drop initially, but there should be more options to customize the UI based on our needs."
"The documentation needs improvement, as it is not user-friendly and can be challenging for novices."
"Its capability to handle big projects needs to be improved. If you generate a user interface in Figma and import everything where all components are in one directory, currently, it is complicated. It isn't able to cope with that. For small projects, it is not an issue, but if you have big projects and you want to use AWS Amplify, then it gets more difficult. That is the most important point for me. It should be improved to cope better with bigger projects."
"Requirements management is an area that can be improved."
"The test management section needs to be improved."
"I would like to see more customization available to the administrator."
"The functions have too much dependency right now, so it makes it really, really hard to upgrade and make a change in the code."
"There is only one key area of improvement for me. The new imaging thing is that there is DevOps, where security is important because it is always lasting. So, to integrate security in our DevOps, that would be nice."
"It would be great if I could integrate with a human resource type of software that could control timesheets."
"When you compare with Jira, there is a lack of progress features."
"A notable improvement would be adding more notifications."
 

Pricing and Cost Advice

"When you're just starting, it is free. You have to pay only when you reach a certain amount of usage. I'm still at the early stage. So, I don't have to pay a lot. At the moment, it is not too expensive for me. It is worth the money."
"The pricing depends on what your use case is and whether you're an existing AWS customer. It's a pay-as-you-go model, so not expensive."
"The solution costs $5 or $10 per user, per month."
"The price of this solution is fair."
"The price is cheaper than Jira and some of the other competing tools."
"It is a subscription model and I only pay for what I use."
"We have an MPN subscription for Microsoft Azure DevOps, and it's all included."
"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."
"It has an annual subscription. It can be cheaper for partners. Many open-source products are available in the market, and it would be great if they can be a little bit more competitive in terms of pricing. A lot of startups are looking for an open-source, free, or cheap solution. If they can accommodate such requirements, it will be good for the product in the long run."
"It is relatively inexpensive compared to other solutions that necessitate servers and physical hardware."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
824,053 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
14%
Financial Services Firm
14%
Manufacturing Company
10%
Construction Company
6%
Manufacturing Company
13%
Computer Software Company
12%
Financial Services Firm
12%
Government
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

How to estimate whether using the AWS services is worthwhile for saving time and money for manufacturing at a retailer company?
Estimating the cost-effectiveness of using AWS services for manufacturing at a retailer company involves a comprehensive analysis. To make an informed decision, you should consider factors like the...
What do you like most about AWS Amplify?
Typically, whenever we make changes and need to switch environments (e.g., dev to production), it's easy for our developers to maintain the state of each environment and make customizations as need...
What is your experience regarding pricing and costs for AWS Amplify?
I find the pricing of AWS Amplify reasonable, considering the value it provides, although opinions may vary based on usage.
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 Amplify vs. Microsoft Azure DevOps and other solutions. Updated: December 2024.
824,053 professionals have used our research since 2012.