TrustRadius: an HG Insights company

Azure DevOps vs. Azure Kubernetes Service (AKS) vs. Kubernetes

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    Azure DevOps

    Score8.1 out of 10
    N/AAzure 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)

    Azure Kubernetes Service (AKS)

    Score8.3 out of 10
    N/AMicrosoft's Azure Kubernetes Service (AKS) is designed to make deploying and managing containerized applications easy. It offers serverless Kubernetes, an integrated continuous integration and continuous delivery (CI/CD) experience, and enterprise-grade security and governance. It allows development and operations teams on a single platform to rapidly build, deliver, and scale applications with confidence.N/A

    Kubernetes

    Score9.1 out of 10
    N/AKubernetes is an open-source container cluster manager.N/A
    Pricing
    Azure DevOpsAzure Kubernetes Service (AKS)Kubernetes
    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
    No answers on this topic
    Offerings
    Pricing Offerings
    Azure DevOpsAzure Kubernetes Service (AKS)Kubernetes
    Free Trial
    NoNoNo
    Free/Freemium Version
    NoNoNo
    Premium Consulting/Integration Services
    NoNoNo
    Entry-level Setup FeeNo setup feeNo setup feeNo setup fee
    Additional Details———
    More Pricing Information
    Community Pulse
    Azure DevOpsAzure Kubernetes Service (AKS)Kubernetes
    Considered Multiple Products
    Microsoft
    Chose Azure DevOps
    Graphically it overtakes the grade of traceability of artifacts delivered to environments More user-friendly to orchestrate the deliveries.
    Incentivized
    Chose Azure DevOps
    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 …
    Incentivized
    Chose Azure DevOps
    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 …
    Incentivized
    Microsoft
    Chose Azure Kubernetes Service (AKS)
    Amazon EKS stacked up very well and had better performance in some areas. However, Azure Kubernetes Service was a better fit given our Azure environment.
    Incentivized
    Chose Azure Kubernetes Service (AKS)
    AKS is more powerful than Azure App Service for containers, but it is also very complex. It is great for running large container-based applications and microservices, but you need some Kubernetes knowledge to manage it. When compared to EKS, both AKS & Azure App Service are …
    Incentivized
    Chose Azure Kubernetes Service (AKS)
    Straight from the beginning, the Github connections are simpler, the permissions and access for users is simpler. Certificate renewal doesn't need to be a worry. There is an option of node-auto provisioning.

    Azure Kubernetes Service (AKS) makes you do all of the above with less …
    Incentivized
    Chose Azure Kubernetes Service (AKS)
    Integration with other standard azure services make Azure Kubernetes Service (AKS) case strong. As we use most of the azure services it is easy to integrate. It is difficult to use EKS as the user interface is not intuitive and difficult to integrate. The services need to be …
    Incentivized
    Chose Azure Kubernetes Service (AKS)
    Due to cost efficiency. And using AZURE cloud for other services as well. Azure Kubernetes Service is more suitable to configure CI/CD pipelines. With a facility of automated or One click deployment and integration of the application. As compared with other Kubernetes Services …
    Incentivized
    Chose Azure Kubernetes Service (AKS)
    The ability to create new instances (i.e. elastic provisioning) is probably the fastest with Azure Kubernetes Service compared to the alternatives that I have looked at. From a pricing perspective, Microsoft always seems to find a way to be more competitive in this area, and …
    Incentivized
    Chose Azure Kubernetes Service (AKS)
    This depends fully on your needs respectively what you expect or the amount of work you can deal with.
    Both services are not the silver bullet that will take care of all your pain points. It is needed to analyze/evaluate them carefully and then decide which makes the most …
    Incentivized
    Kubernetes
    Chose Kubernetes
    I didn't have too much experience or exposure to OpenShift but I do remember that in certain areas our organization found Kubernetes to be more useful and met our needs in comparison to OpenShift. Although I can't compare, I think it's easier to customize Kubernetes because of …
    Incentivized
    Key User Insights
    Would buy again
    97%
    Would buy again
    38 Answers
    90%
    Would buy again
    9 Answers
    100%
    Would buy again
    9 Answers
    Delivers good value for the price
    100%
    Delivers good value for the price
    37 Answers
    90%
    Delivers good value for the price
    9 Answers
    100%
    Delivers good value for the price
    9 Answers
    Happy with the feature set
    100%
    Happy with the feature set
    39 Answers
    80%
    Happy with the feature set
    8 Answers
    100%
    Happy with the feature set
    9 Answers
    Lived up to sales and marketing promises
    96%
    Lived up to sales and marketing promises
    23 Answers
    100%
    Lived up to sales and marketing promises
    6 Answers
    100%
    Lived up to sales and marketing promises
    5 Answers
    Implementation went as expected
    100%
    Implementation went as expected
    32 Answers
    78%
    Implementation went as expected
    7 Answers
    75%
    Implementation went as expected
    6 Answers
    Features
    Azure DevOpsAzure Kubernetes Service (AKS)Kubernetes
    Container Management
    Comparison of Container Management features of Azure DevOps and Azure Kubernetes Service (AKS) and Kubernetes
    Feature
    Azure DevOps
    -
    Ratings
    Azure Kubernetes Service (AKS)
    7.8
    5 Ratings
    5% below category average
    Kubernetes
    9.3
    4 Ratings
    13% above category average
    Security and Isolation00 Ratings8.75 Ratings9.34 Ratings
    Container Orchestration00 Ratings8.05 Ratings9.84 Ratings
    Cluster Management00 Ratings8.05 Ratings9.84 Ratings
    Storage Management00 Ratings7.85 Ratings8.64 Ratings
    Resource Allocation and Optimization00 Ratings7.85 Ratings8.84 Ratings
    Discovery Tools00 Ratings7.25 Ratings9.34 Ratings
    Update Rollouts and Rollbacks00 Ratings7.05 Ratings9.34 Ratings
    Self-Healing and Recovery00 Ratings8.25 Ratings9.33 Ratings
    Analytics, Monitoring, and Logging00 Ratings7.55 Ratings9.14 Ratings
    Best Alternatives
    Azure DevOpsAzure Kubernetes Service (AKS)Kubernetes
    Small Businesses
    No answers on this topic
    Mirantis Kubernetes Engine
    Score8 out of 10
    Mirantis Kubernetes Engine
    Score8 out of 10
    Medium-sized Companies
    Azure DevOps Server
    Score8.5 out of 10
    Amazon Elastic Container Service (Amazon ECS)
    Score8.6 out of 10
    Amazon Elastic Container Service (Amazon ECS)
    Score8.6 out of 10
    Enterprises
    Azure DevOps Server
    Score8.5 out of 10
    SUSE Rancher
    Score9.4 out of 10
    SUSE Rancher
    Score9.4 out of 10
    All AlternativesView all alternativesView all alternativesView all alternatives
    User Ratings
    Azure DevOpsAzure Kubernetes Service (AKS)Kubernetes
    Likelihood to Recommend
    8.9
    (74 ratings)
    8.4
    (10 ratings)
    8.7
    (19 ratings)
    Likelihood to Renew
    10.0
    (3 ratings)
    -
    (0 ratings)
    10.0
    (1 ratings)
    Usability
    8.4
    (13 ratings)
    7.7
    (5 ratings)
    9.1
    (3 ratings)
    Support Rating
    8.1
    (11 ratings)
    9.0
    (1 ratings)
    -
    (0 ratings)
    Implementation Rating
    10.0
    (1 ratings)
    -
    (0 ratings)
    -
    (0 ratings)
    User Testimonials
    Azure DevOpsAzure Kubernetes Service (AKS)Kubernetes
    Likelihood to Recommend
    Microsoft
    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.
    Incentivized
    Read full review
    Microsoft
    AKS works very well for running containerized applications that require high availability and scalability. This includes systems like our HRIS platform and customer-facing web applications. AKS is a good choice when applications are broken into multiple services that need independent scaling and deployment. It provides the flexibility needed to manage these architectures effectively. But for single, low-traffic applications or simple internal tools, AKS can be overkill. For scenarios like that Azure App Service would be better.
    Incentivized
    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.
    Incentivized
    Read full review
    Pros
    Microsoft
    • Utilize Git as a repository to share work between multiple users
    • Ability to configure Pipelines to build containers to run virtual deployments and testing scripts.
    • Split individual tasks and relate to master documents for quick navigation and ability to see overall picture of project.
    • Track status of each task
    • Integrate with Git to utilize branches, merging, approvals, history, etc.
    Incentivized
    Read full review
    Microsoft
    • AKS makes it easier to replicate data to multiple regions
    • Azure portal make it easier to manage the resources of the organization
    Incentivized
    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
    Incentivized
    Read full review
    Cons
    Microsoft
    • 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.
    • It could improve the search slightly better.
    Read full review
    Microsoft
    • Steep learning curve
    • Expected charges are unclear until you see real production usage
    • Operations teams need to learn an entirely new skill set
    Incentivized
    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.
    Incentivized
    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.
    Incentivized
    Read full review
    Microsoft
    No answers on this topic
    Kubernetes
    The Kubernetes is going to be highly likely renewed as the technologies that will be placed on top of it are long term as of planning. There shouldn't be any last minute changes in the adoption and I do not anticipate sudden change of the core underlying technology. It is just that the slow process of technology adoption that makes it hard to switch to something else.
    Read full review
    Usability
    Microsoft
    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.).
    Incentivized
    Read full review
    Microsoft
    As already said, the UI/CLI and even terraform are perfectly fine, but certain details could be documented better. For instance, if I want to secure the whole Azure Kubernetes Service (AKS) with my own managed keys, then it is very complex and hard to get there. Not really a single source that gives you the whole picture. Besides that, it is still good to use, in most cases intuitive but details mentioned as above can be tricky.
    Incentivized
    Read full review
    Kubernetes
    It is an eminently usable platform. However, its popularity is overshadowed by its complexity. To properly leverage the capabilities and possibilities of Kubernetes as a platform, you need to have excellent understanding of your use case, even better understanding of whether you even need Kubernetes, and if yes - be ready to invest in good engineering support for the platform itself
    Incentivized
    Read full review
    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.
    Incentivized
    Read full review
    Microsoft
    Microsoft support was really good, whenever we raise any ticket they come back to us within a couple of hours.
    Incentivized
    Read full review
    Kubernetes
    No answers on this topic
    Implementation Rating
    Microsoft
    Was not part of the process.
    Incentivized
    Read full review
    Microsoft
    No answers on this topic
    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.
    Incentivized
    Read full review
    Microsoft
    Amazon EKS stacked up very well and had better performance in some areas. However, Azure Kubernetes Service was a better fit given our Azure environment.
    Incentivized
    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.
    Incentivized
    Read full review
    Return on Investment
    Microsoft
    • 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.
    Incentivized
    Read full review
    Microsoft
    • We had to spend more time on Azure Kubernetes Service (AKS) than on AWS and GCP to get our kubernetes cluster up and running
    • The resources on nodes need to be left out unused, so effectively it is wasting money there
    • It definitely made us spend more time into maintaining kubernetes
    Incentivized
    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.
    Incentivized
    Read full review
    ScreenShots