Amazon Web Services (AWS) is a subsidiary of Amazon that provides on-demand cloud computing services. With over 165 services offered, AWS services can provide users with a comprehensive suite of infrastructure and computing building blocks and tools.
$100
per month
Azure DevOps
Score 8.1 out of 10
N/A
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Pricing
Amazon Web Services
Azure DevOps
Editions & Modules
Free Tier
$0
per month
Basic Environment
$100 - $200
per month
Intermediate Environment
$250 - $600
per month
Advanced Environment
$600-$2500
per month
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
Basic + Test Plan
$52
per user per month
Offerings
Pricing Offerings
Amazon Web Services
Azure DevOps
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
AWS allows a “save when you commit” option that offers lower prices when you sign up for a 1- or 3- year term that includes an AWS service or category of services.
AWS has more APIs to use on the cloud. Microsoft has an API mainly for the Microsoft platform. And Google has different big data analytics than other competitors [do].
Easier to use than GitHub, but it comes at a cost. Although you can script VSTS, the online version could use a more substantial editor. Those who remember project Monaco and its current implementation in Azure, App Service Editor, will be disappointed if looking for more of …
This is something that is actually common across most cloud providers. A comprehensive understanding of one's use cases, constraints and future directions is key to determining if you even need a cloud solution. If you are a 2-person startup developing something with a best-scenario audience of 1k DAU in a year, you would very likely best served by a dirt-cheap dedicated Linux server somewhere (and your options to graduate to a cloud solution will still be open). If, however, you are a bigger fish, and/or you are actively considering build-vs-buy decisions for complicated, highly-loaded, six-figure requests per minute systems, global loadbalancing, extreme growth projections - then MAYBE you solve all or part of it with a cloud provider. And depending on your taste for risk, reliability, flexibility, track record - it might be AWS.
Azure DevOps works well when you’ve got larger delivery efforts with multiple teams and a lot of moving parts, and you need one place to plan work, track it properly, and see how everything links together. It’s especially useful when delivery and development are closely tied and you want backlog items, code and releases connected rather than spread across tools. Where it’s less of a fit is for small teams or simple pieces of work, as it can feel like more setup and process than you really need, and non-technical users often struggle with the interface. It also isn’t great if you want instant, easy programme-level views or a very visual planning experience without putting time into configuration.
I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
The wiki is not the prettiest thing to look at, so it could have refinements there.
We are almost entirely satisfied with the service. In order to move off it, we'd have to build for ourselves many of the services that AWS provides and the cost would be prohibitive. Although there are cost savings and security benefits to returning to the colo facility, we could never afford to do it, and we'd hate to give up the innovation and constant cycle of new features that AWS gives us.
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
AWS offers a wide range of powerful services that cater to various business needs which is significant strength. The ability to scale resources on-demand is a major advantage making it suitable for businesses of all sizes. The sheer volume of options and configurations can be overwhelming for new users leading to a steep learning curve. While functional the AWS management console can feel cluttered and less intuitive compared to some competitors which can hinder navigation. Although some documentation lacks clarity and practical examples which can frustrate users trying to implement specific solutions.
It's a great help to get more information about new feature release and stay updated on what the dev team is working on. I like how easy it is to just login and read through the work items. Each work item has basic details: Title, Description, Assigned to, State, Area (what it belongs to), and iteration (when it’s worked on). See image above.They move through different states (New → Discovery → Ready for Prod → etc.).
AWS does not provide the raw performance that you can get by building your own custom infrastructure. However, it is often the case that the benefits of specialized, high-performance hardware do not necessarily outweigh the significant extra cost and risk. Performance as perceived by the user is very different from raw throughput.
The customer support of Amazon Web Services are quick in their responses. I appreciate its entire team, which works amazingly, and provides professional support. AWS is a great tool, indeed, to provide customers a suitable way to immediately search for their compatible software's and also to guide them in a good direction. Moreover, this product is a good suggestion for every type of company because of its affordability and ease of use.
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
Amazon Web Services fits best for all levels of organisations like startup, mid level or enterprise. The services are easy to use and doesn't require a high level of understanding as you can learn via blogs or youtube videos. AWS is Reasonable in cost as the plan is pay as you use.
Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or more business-focused projects. We also use ServiceNow for IT service management and this tool provides better analysis and tracking of IT incidents, as Azure DevOps is more suited to development and project work for dev teams.
Using Amazon Web Services has allowed us to develop and deploy new SAAS solutions quicker than we did when we used traditional web hosting. This has allowed us to grow our service offerings to clients and also add more value to our existing services.
Having AWS deployed has also allowed our development team to focus on delivering high-quality software without worrying about whether our servers will be able to handle the demand. Since AWS allows you to adjust your server needs based on demand, we can easily assign a faster server instance to ease and improve service without the client even knowing what we did.
We have saved a ton of time not calculating metrics by hand.
We no longer spend time writing out cards during planning, it goes straight to the board.
We no longer track separate documents to track overall department goals. We were able to create customized icons at the department level that lets us track each team's progress against our dept goals.