Azure DevOps Services vs. Kubernetes

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Azure DevOps Services
Score 8.5 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)
Kubernetes
Score 8.8 out of 10
N/A
Kubernetes is an open-source container cluster manager.N/A
Pricing
Azure DevOps ServicesKubernetes
Editions & Modules
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
No answers on this topic
Offerings
Pricing Offerings
Azure DevOps ServicesKubernetes
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
Community Pulse
Azure DevOps ServicesKubernetes
Considered Both Products
Azure DevOps Services
Chose Azure DevOps Services
Graphically it overtakes the grade of traceability of artifacts delivered to environments More user-friendly to orchestrate the deliveries.
Chose Azure DevOps Services
One of the foremost reasons that acted in favor of Azure DevOps was its all-in-one packed web portal which enabled easy access to all the CI/CD tools and kits. Customizable screens, notifications via Teams/mails, project views, etc. Most other tools/products offer only part of …
Chose Azure DevOps Services
Azure DevOps required the least amount of up front knowledge to get a pipeline up and running. Because of the built in activities, when I initially started working with this tool I didn't have to know anything other than where my code was stored. The rest was easy enough to …
Kubernetes

No answer on this topic

Top Pros
Top Cons
Features
Azure DevOps ServicesKubernetes
Container Management
Comparison of Container Management features of Product A and Product B
Azure DevOps Services
-
Ratings
Kubernetes
7.8
1 Ratings
1% below category average
Security and Isolation00 Ratings10.01 Ratings
Container Orchestration00 Ratings7.01 Ratings
Cluster Management00 Ratings9.01 Ratings
Storage Management00 Ratings9.01 Ratings
Resource Allocation and Optimization00 Ratings8.01 Ratings
Discovery Tools00 Ratings5.01 Ratings
Update Rollouts and Rollbacks00 Ratings5.01 Ratings
Analytics, Monitoring, and Logging00 Ratings9.01 Ratings
Best Alternatives
Azure DevOps ServicesKubernetes
Small Businesses
Docker
Docker
Score 9.1 out of 10
IBM Cloud Kubernetes Service
IBM Cloud Kubernetes Service
Score 9.4 out of 10
Medium-sized Companies
AWS CodePipeline
AWS CodePipeline
Score 9.2 out of 10
IBM Cloud Kubernetes Service
IBM Cloud Kubernetes Service
Score 9.4 out of 10
Enterprises
AWS CodePipeline
AWS CodePipeline
Score 9.2 out of 10
IBM Cloud Kubernetes Service
IBM Cloud Kubernetes Service
Score 9.4 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Azure DevOps ServicesKubernetes
Likelihood to Recommend
8.8
(66 ratings)
8.9
(16 ratings)
Likelihood to Renew
10.0
(3 ratings)
-
(0 ratings)
Usability
7.0
(5 ratings)
-
(0 ratings)
Support Rating
8.1
(11 ratings)
-
(0 ratings)
Implementation Rating
10.0
(1 ratings)
-
(0 ratings)
User Testimonials
Azure DevOps ServicesKubernetes
Likelihood to Recommend
Microsoft
ADO is well suited for the visibility of day-to-day tasks and responsibilities as well as things such as Features, user stories, etc. Off the top of my head, I can't think of any scenario where it might not be well suited, as you can customize ADO to your liking to a degree.
Read full review
Kubernetes
K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.
Read full review
Pros
Microsoft
  • Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
  • Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
  • Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.
Read full review
Kubernetes
  • Complex cluster management can be done with simple commands with strong authentication and authorization schemes
  • Exhaustive documentation and open community smoothens the learning process
  • As a user a few concepts like pod, deployment and service are sufficient to go a long way
Read full review
Cons
Microsoft
  • Column sorting when in filtered states.
  • A way to show cross-team dependencies.
  • A customized "From" field for notifications. Sometimes when a mail comes from Azure DevOps the teams do not realize that I am sending it
  • A way to do online poker that doesn't require a plug-in.
Read full review
Kubernetes
  • Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
  • The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
  • Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.
Read full review
Likelihood to Renew
Microsoft
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.
Read full review
Kubernetes
No answers on this topic
Usability
Microsoft
Azure DevOps is a powerful, complex cloud application. As such there are a number of things it does great and something where there is room for improvement. One of those areas would be in usability. In my opinion it relies too much on search. There is no easy way to view all projects or to group them in a logical way. You need to search for everything.
Read full review
Kubernetes
No answers on this topic
Support Rating
Microsoft
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.
Read full review
Kubernetes
No answers on this topic
Implementation Rating
Microsoft
Was not part of the process.
Read full review
Kubernetes
No answers on this topic
Alternatives Considered
Microsoft
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.
Read full review
Kubernetes
Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.
Read full review
Return on Investment
Microsoft
  • It provides a great IDE to make things easier, clear, and compact. It has always been a positive ROI
  • It's worth the money. I don't think any other software could replace the VS. It has helped us a lot to making things ready on time
  • The only thing I dislike is that it takes a lot of memory space when in an idle state
Read full review
Kubernetes
  • Because of microservices, Kubernetes makes it easy to find the cost of each application easily.
  • Like every new technology, initially, it took more resources to educate ourselves but over a period of time, I believe it's going to be worth it.
Read full review
ScreenShots