TrustRadius: an HG Insights company

Azure Kubernetes Service (AKS) vs. Google Cloud Spanner vs. Kubernetes

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    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

    Google Cloud Spanner

    Score5.6 out of 10
    N/AGoogle Cloud Spanner is a cloud database-as-a-service product offered as a service on Google Cloud Platform (GCP).N/A

    Kubernetes

    Score9.1 out of 10
    N/AKubernetes is an open-source container cluster manager.N/A
    Pricing
    Azure Kubernetes Service (AKS)Google Cloud SpannerKubernetes
    Editions & Modules
    No answers on this topic
    No answers on this topic
    No answers on this topic
    Offerings
    Pricing Offerings
    Azure Kubernetes Service (AKS)Google Cloud SpannerKubernetes
    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 Kubernetes Service (AKS)Google Cloud SpannerKubernetes
    Considered Multiple Products
    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
    Google
    No answer on this topic
    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
    90%
    Would buy again
    9 Answers
    No answers on this topic
    100%
    Would buy again
    9 Answers
    Delivers good value for the price
    90%
    Delivers good value for the price
    9 Answers
    No answers on this topic
    100%
    Delivers good value for the price
    9 Answers
    Happy with the feature set
    80%
    Happy with the feature set
    8 Answers
    No answers on this topic
    100%
    Happy with the feature set
    9 Answers
    Lived up to sales and marketing promises
    100%
    Lived up to sales and marketing promises
    6 Answers
    No answers on this topic
    100%
    Lived up to sales and marketing promises
    5 Answers
    Implementation went as expected
    78%
    Implementation went as expected
    7 Answers
    No answers on this topic
    75%
    Implementation went as expected
    6 Answers
    Features
    Azure Kubernetes Service (AKS)Google Cloud SpannerKubernetes
    Container Management
    Comparison of Container Management features of Azure Kubernetes Service (AKS) and Google Cloud Spanner and Kubernetes
    Feature
    Azure Kubernetes Service (AKS)
    7.8
    5 Ratings
    5% below category average
    Google Cloud Spanner
    -
    Ratings
    Kubernetes
    9.2
    4 Ratings
    12% above category average
    Security and Isolation8.75 Ratings00 Ratings9.34 Ratings
    Container Orchestration8.05 Ratings00 Ratings9.84 Ratings
    Cluster Management8.05 Ratings00 Ratings9.84 Ratings
    Storage Management7.85 Ratings00 Ratings8.64 Ratings
    Resource Allocation and Optimization7.95 Ratings00 Ratings8.84 Ratings
    Discovery Tools7.25 Ratings00 Ratings9.34 Ratings
    Update Rollouts and Rollbacks7.05 Ratings00 Ratings9.34 Ratings
    Self-Healing and Recovery8.15 Ratings00 Ratings9.33 Ratings
    Analytics, Monitoring, and Logging7.55 Ratings00 Ratings9.14 Ratings
    Database-as-a-Service
    Comparison of Database-as-a-Service features of Azure Kubernetes Service (AKS) and Google Cloud Spanner and Kubernetes
    Feature
    Azure Kubernetes Service (AKS)
    -
    Ratings
    Google Cloud Spanner
    7.8
    2 Ratings
    8% below category average
    Kubernetes
    -
    Ratings
    Automatic software patching00 Ratings8.82 Ratings00 Ratings
    Database scalability00 Ratings8.82 Ratings00 Ratings
    Automated backups00 Ratings10.01 Ratings00 Ratings
    Database security provisions00 Ratings5.82 Ratings00 Ratings
    Monitoring and metrics00 Ratings5.82 Ratings00 Ratings
    Automatic host deployment00 Ratings7.62 Ratings00 Ratings
    Best Alternatives
    Azure Kubernetes Service (AKS)Google Cloud SpannerKubernetes
    Small Businesses
    Mirantis Kubernetes Engine
    Score8 out of 10
    MongoDB Atlas
    Score7.8 out of 10
    Mirantis Kubernetes Engine
    Score8 out of 10
    Medium-sized Companies
    Amazon Elastic Container Service (Amazon ECS)
    Score8.6 out of 10
    Azure Database
    Score8.8 out of 10
    Amazon Elastic Container Service (Amazon ECS)
    Score8.6 out of 10
    Enterprises
    SUSE Rancher
    Score9.4 out of 10
    Google Cloud SQL
    Score8.7 out of 10
    SUSE Rancher
    Score9.4 out of 10
    All AlternativesView all alternativesView all alternativesView all alternatives
    User Ratings
    Azure Kubernetes Service (AKS)Google Cloud SpannerKubernetes
    Likelihood to Recommend
    8.4
    (10 ratings)
    7.4
    (2 ratings)
    8.7
    (19 ratings)
    Likelihood to Renew
    -
    (0 ratings)
    -
    (0 ratings)
    10.0
    (1 ratings)
    Usability
    7.7
    (5 ratings)
    -
    (0 ratings)
    9.1
    (3 ratings)
    Support Rating
    9.0
    (1 ratings)
    -
    (0 ratings)
    -
    (0 ratings)
    User Testimonials
    Azure Kubernetes Service (AKS)Google Cloud SpannerKubernetes
    Likelihood to Recommend
    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
    Google
    Google Cloud Spanner is suited for limitless horizontal scaling while maintaining strong consistency which needs to support ACID. NoSQL databases work in scaling but no ACID support. RDBMS support ACID, but horizontal scaling is not as great. The API it provides result in some limitations to related areas of the code, such as connection pools or database linking framework. So high # of connection pools can vary.
    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
    • 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
    Google
    • Super high availability
    • Scales automatically
    • High standard SLA
    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
    • 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
    Google
    • Support for Views
    • Support for more databases (schemas).
    • More index types that can be supported (Functional)
    • Backups (ie table/data backup) if data is deleted or truncate by accident.
    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
    No answers on this topic
    Google
    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
    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
    Google
    No answers on this topic
    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
    Microsoft support was really good, whenever we raise any ticket they come back to us within a couple of hours.
    Incentivized
    Read full review
    Google
    No answers on this topic
    Kubernetes
    No answers on this topic
    Alternatives Considered
    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
    Google
    At that point, we were looking at something [that] can hold our relational database, [...] provide stable connection, and maintain high ACID transition. BigTable is for nonrelational database so it was out of our [sight] very quickly. BigQuery is a data warehouse that can hold huge amount of data but not ideal for transition. AWS RDS is [...] similar to Spanner but because most of our services are already on GCP, so we went with Spanner.
    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 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
    Google
    • Backups specifically if transactional data is deleted. Restoring made us lose time.
    • Sharding on Horizontal level was quick and easy. Deployment and increasing nodes is easy
    • Large dataset handling.
    • ACID compliance
    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