Alternatives to Google Kubernetes Engine logo

Alternatives to Google Kubernetes Engine

Google App Engine, Red Hat OpenShift, Google Compute Engine, Kubernetes, and Amazon EC2 Container Service are the most popular alternatives and competitors to Google Kubernetes Engine.
1K
708
+ 1
69

What is Google Kubernetes Engine and what are its top alternatives?

Container Engine takes care of provisioning and maintaining the underlying virtual machine cluster, scaling your application, and operational logistics like logging, monitoring, and health management.
Google Kubernetes Engine is a tool in the Containers as a Service category of a tech stack.

Top Alternatives to Google Kubernetes Engine

  • Google App Engine

    Google App Engine

    Google has a reputation for highly reliable, high performance infrastructure. With App Engine you can take advantage of the 10 years of knowledge Google has in running massively scalable, performance driven systems. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow. ...

  • Red Hat OpenShift

    Red Hat OpenShift

    OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications. ...

  • Google Compute Engine

    Google Compute Engine

    Google Compute Engine is a service that provides virtual machines that run on Google infrastructure. Google Compute Engine offers scale, performance, and value that allows you to easily launch large compute clusters on Google's infrastructure. There are no upfront investments and you can run up to thousands of virtual CPUs on a system that has been designed from the ground up to be fast, and to offer strong consistency of performance. ...

  • Kubernetes

    Kubernetes

    Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions. ...

  • Amazon EC2 Container Service

    Amazon EC2 Container Service

    Amazon EC2 Container Service lets you launch and stop container-enabled applications with simple API calls, allows you to query the state of your cluster from a centralized service, and gives you access to many familiar Amazon EC2 features like security groups, EBS volumes and IAM roles. ...

  • Amazon EKS

    Amazon EKS

    Amazon Elastic Container Service for Kubernetes (Amazon EKS) is a managed service that makes it easy for you to run Kubernetes on AWS without needing to install and operate your own Kubernetes clusters. ...

  • AWS Fargate

    AWS Fargate

    AWS Fargate is a technology for Amazon ECS and EKS* that allows you to run containers without having to manage servers or clusters. With AWS Fargate, you no longer have to provision, configure, and scale clusters of virtual machines to run containers. ...

  • Azure Kubernetes Service

    Azure Kubernetes Service

    Deploy and manage containerized applications more easily with a fully managed Kubernetes service. It offers serverless Kubernetes, an integrated continuous integration and continuous delivery (CI/CD) experience, and enterprise-grade security and governance. Unite your development and operations teams on a single platform to rapidly build, deliver, and scale applications with confidence. ...

Google Kubernetes Engine alternatives & related posts

Google App Engine logo

Google App Engine

7.4K
5.7K
612
Build web applications on the same scalable systems that power Google applications
7.4K
5.7K
+ 1
612
PROS OF GOOGLE APP ENGINE
  • 144
    Easy to deploy
  • 108
    Auto scaling
  • 80
    Good free plan
  • 64
    Easy management
  • 58
    Scalability
  • 35
    Low cost
  • 33
    Comprehensive set of features
  • 29
    All services in one place
  • 23
    Simple scaling
  • 20
    Quick and reliable cloud servers
  • 5
    Granular Billing
  • 4
    Easy to develop and unit test
  • 3
    Monitoring gives comprehensive set of key indicators
  • 2
    Create APIs quickly with cloud endpoints
  • 2
    Really easy to quickly bring up a full stack
  • 1
    Mostly up
  • 1
    No Ops
CONS OF GOOGLE APP ENGINE
    Be the first to leave a con

    related Google App Engine posts

    Nick Rockwell
    SVP, Engineering at Fastly · | 11 upvotes · 284.9K views

    So, the shift from Amazon EC2 to Google App Engine and generally #AWS to #GCP was a long decision and in the end, it's one that we've taken with eyes open and that we reserve the right to modify at any time. And to be clear, we continue to do a lot of stuff with AWS. But, by default, the content of the decision was, for our consumer-facing products, we're going to use GCP first. And if there's some reason why we don't think that's going to work out great, then we'll happily use AWS. In practice, that hasn't really happened. We've been able to meet almost 100% of our needs in GCP.

    So it's basically mostly Google Kubernetes Engine , we're mostly running stuff on Kubernetes right now.

    #AWStoGCPmigration #cloudmigration #migration

    See more
    Aliadoc Team

    In #Aliadoc, we're exploring the crowdfunding option to get traction before launch. We are building a SaaS platform for website design customization.

    For the Admin UI and website editor we use React and we're currently transitioning from a Create React App setup to a custom one because our needs have become more specific. We use CloudFlare as much as possible, it's a great service.

    For routing dynamic resources and proxy tasks to feed websites to the editor we leverage CloudFlare Workers for improved responsiveness. We use Firebase for our hosting needs and user authentication while also using several Cloud Functions for Firebase to interact with other services along with Google App Engine and Google Cloud Storage, but also the Real Time Database is on the radar for collaborative website editing.

    We generally hate configuration but honestly because of the stage of our project we lack resources for doing heavy sysops work. So we are basically just relying on Serverless technologies as much as we can to do all server side processing.

    Visual Studio Code definitively makes programming a much easier and enjoyable task, we just love it. We combine it with Bitbucket for our source code control needs.

    See more
    Red Hat OpenShift logo

    Red Hat OpenShift

    1.1K
    1.2K
    480
    Red Hat's free Platform as a Service (PaaS) for hosting Java, PHP, Ruby, Python, Node.js, and Perl apps
    1.1K
    1.2K
    + 1
    480
    PROS OF RED HAT OPENSHIFT
    • 97
      Good free plan
    • 61
      Open Source
    • 45
      Easy setup
    • 41
      Nodejs support
    • 39
      Well documented
    • 31
      Custom domains
    • 27
      Mongodb support
    • 26
      Clean and simple architecture
    • 24
      PHP support
    • 20
      Customizable environments
    • 10
      Ability to run CRON jobs
    • 8
      Easier than Heroku for a WordPress blog
    • 6
      PostgreSQL support
    • 6
      Autoscaling
    • 6
      Easy deployment
    • 6
      Good balance between Heroku and AWS for flexibility
    • 5
      Free, Easy Setup, Lot of Gear or D.I.Y Gear
    • 4
      Shell access to gears
    • 3
      Great Support
    • 2
      Overly complicated and over engineered in majority of e
    • 2
      Golang support
    • 2
      Its free and offer custom domain usage
    • 1
      Meteor support
    • 1
      Easy setup and great customer support
    • 1
      High Security
    • 1
      No credit card needed
    • 1
      because it is easy to manage
    • 1
      Logging & Metrics
    • 1
      Autoscaling at a good price point
    • 1
      Great free plan with excellent support
    • 1
      This is the only free one among the three as of today
    CONS OF RED HAT OPENSHIFT
    • 2
      Decisions are made for you, limiting your options
    • 2
      License cost
    • 1
      Behind, sometimes severely, the upstreams

    related Red Hat OpenShift posts

    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 39 upvotes · 4.3M views

    How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

    Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

    Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

    https://eng.uber.com/distributed-tracing/

    (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

    Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

    See more
    Michael Ionita

    We use Kubernetes because we decided to migrate to a hosted cluster (not AWS) and still be able to scale our clusters up and down depending on load. By wrapping it with OpenShift we are now able to easily adapt to demand but also able to separate concerns into separate Pods depending on use-cases we have.

    See more
    Google Compute Engine logo

    Google Compute Engine

    9.1K
    6.6K
    425
    Run large-scale workloads on virtual machines hosted on Google's infrastructure.
    9.1K
    6.6K
    + 1
    425
    PROS OF GOOGLE COMPUTE ENGINE
    • 88
      Backed by google
    • 80
      Easy to scale
    • 75
      High-performance virtual machines
    • 58
      Performance
    • 52
      Fast and easy provisioning
    • 15
      Load balancing
    • 12
      Compliance and security
    • 9
      Kubernetes
    • 8
      GitHub Integration
    • 7
      Consistency
    • 3
      Good documentation
    • 3
      One Click Setup Options
    • 3
      Free $300 credit (12 months)
    • 2
      Ease of Use and GitHub support
    • 2
      Great integration and product support
    • 2
      Escort
    • 1
      Integration with mobile notification services
    • 1
      Easy Snapshot and Backup feature
    • 1
      Low cost
    • 1
      Support many OS
    • 1
      Very Reliable
    • 1
      Nice UI
    CONS OF GOOGLE COMPUTE ENGINE
      Be the first to leave a con

      related Google Compute Engine posts

      Kestas Barzdaitis
      Entrepreneur & Engineer · | 16 upvotes · 454.6K views

      CodeFactor being a #SAAS product, our goal was to run on a cloud-native infrastructure since day one. We wanted to stay product focused, rather than having to work on the infrastructure that supports the application. We needed a cloud-hosting provider that would be reliable, economical and most efficient for our product.

      CodeFactor.io aims to provide an automated and frictionless code review service for software developers. That requires agility, instant provisioning, autoscaling, security, availability and compliance management features. We looked at the top three #IAAS providers that take up the majority of market share: Amazon's Amazon EC2 , Microsoft's Microsoft Azure, and Google Compute Engine.

      AWS has been available since 2006 and has developed the most extensive services ant tools variety at a massive scale. Azure and GCP are about half the AWS age, but also satisfied our technical requirements.

      It is worth noting that even though all three providers support Docker containerization services, GCP has the most robust offering due to their investments in Kubernetes. Also, if you are a Microsoft shop, and develop in .NET - Visual Studio Azure shines at integration there and all your existing .NET code works seamlessly on Azure. All three providers have serverless computing offerings (AWS Lambda, Azure Functions, and Google Cloud Functions). Additionally, all three providers have machine learning tools, but GCP appears to be the most developer-friendly, intuitive and complete when it comes to #Machinelearning and #AI.

      The prices between providers are competitive across the board. For our requirements, AWS would have been the most expensive, GCP the least expensive and Azure was in the middle. Plus, if you #Autoscale frequently with large deltas, note that Azure and GCP have per minute billing, where AWS bills you per hour. We also applied for the #Startup programs with all three providers, and this is where Azure shined. While AWS and GCP for startups would have covered us for about one year of infrastructure costs, Azure Sponsorship would cover about two years of CodeFactor's hosting costs. Moreover, Azure Team was terrific - I felt that they wanted to work with us where for AWS and GCP we were just another startup.

      In summary, we were leaning towards GCP. GCP's advantages in containerization, automation toolset, #Devops mindset, and pricing were the driving factors there. Nevertheless, we could not say no to Azure's financial incentives and a strong sense of partnership and support throughout the process.

      Bottom line is, IAAS offerings with AWS, Azure, and GCP are evolving fast. At CodeFactor, we aim to be platform agnostic where it is practical and retain the flexibility to cherry-pick the best products across providers.

      See more
      Mohamed Labouardy

      Google Compute Engine Amazon Web Services OVH Microsoft Azure Go GitHub

      Last week, we released a fresh new release of Komiser with support of multiple AWS accounts. Komiser support multiple AWS accounts through named profiles that are stored in the credentials files.

      You can now analyze and identify potential cost savings on unlimited AWS environments (Production, Staging, Sandbox, etc) on one single dashboard.

      Read the full story in the blog post.

      See more
      Kubernetes logo

      Kubernetes

      39.1K
      33.3K
      628
      Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops
      39.1K
      33.3K
      + 1
      628
      PROS OF KUBERNETES
      • 159
        Leading docker container management solution
      • 124
        Simple and powerful
      • 101
        Open source
      • 75
        Backed by google
      • 56
        The right abstractions
      • 24
        Scale services
      • 18
        Replication controller
      • 9
        Permission managment
      • 7
        Simple
      • 7
        Supports autoscaling
      • 6
        Cheap
      • 4
        Self-healing
      • 4
        Reliable
      • 4
        No cloud platform lock-in
      • 3
        Open, powerful, stable
      • 3
        Scalable
      • 3
        Quick cloud setup
      • 3
        Promotes modern/good infrascture practice
      • 2
        Backed by Red Hat
      • 2
        Runs on azure
      • 2
        Cloud Agnostic
      • 2
        Custom and extensibility
      • 2
        Captain of Container Ship
      • 2
        A self healing environment with rich metadata
      • 1
        Golang
      • 1
        Easy setup
      • 1
        Everything of CaaS
      • 1
        Sfg
      • 1
        Expandable
      • 1
        Gke
      CONS OF KUBERNETES
      • 13
        Poor workflow for development
      • 11
        Steep learning curve
      • 5
        Orchestrates only infrastructure
      • 2
        High resource requirements for on-prem clusters

      related Kubernetes posts

      Conor Myhrvold
      Tech Brand Mgr, Office of CTO at Uber · | 39 upvotes · 4.3M views

      How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

      Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

      Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

      https://eng.uber.com/distributed-tracing/

      (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

      Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

      See more
      Yshay Yaacobi

      Our first experience with .NET core was when we developed our OSS feature management platform - Tweek (https://github.com/soluto/tweek). We wanted to create a solution that is able to run anywhere (super important for OSS), has excellent performance characteristics and can fit in a multi-container architecture. We decided to implement our rule engine processor in F# , our main service was implemented in C# and other components were built using JavaScript / TypeScript and Go.

      Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.

      After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...

      See more
      Amazon EC2 Container Service logo

      Amazon EC2 Container Service

      9.9K
      6.7K
      322
      Container management service that supports Docker containers
      9.9K
      6.7K
      + 1
      322
      PROS OF AMAZON EC2 CONTAINER SERVICE
      • 99
        Backed by amazon
      • 71
        Familiar to ec2
      • 53
        Cluster based
      • 42
        Simple API
      • 26
        Iam roles
      • 7
        Cluster management
      • 7
        Programmatic Control
      • 7
        Scheduler
      • 4
        Socker support
      • 4
        Container-enabled applications
      • 1
        No additional cost
      • 1
        Easy to use and cheap
      CONS OF AMAZON EC2 CONTAINER SERVICE
        Be the first to leave a con

        related Amazon EC2 Container Service posts

        Cyril Duchon-Doris

        We build a Slack app using the Bolt framework from slack https://api.slack.com/tools/bolt, a Node.js express app. It allows us to easily implement some administration features so we can easily communicate with our backend services, and we don't have to develop any frontend app since Slack block kit will do this for us. It can act as a Chatbot or handle message actions and custom slack flows for our employees.

        This app is deployed as a microservice on Amazon EC2 Container Service with AWS Fargate. It uses very little memory (and money) and can communicate easily with our backend services. Slack is connected to this app through a ALB ( AWS Elastic Load Balancing (ELB) )

        See more

        We started using Amazon EC2 Container Service 3 years ago because it was the easiest containers orchestration tool to start with. At the time it was missing a lot of features compared to other tools, but it was still the fastest way to deploy a container on AWS. As with any AWS product, over time they caught up and improved it significantly. Today it probably one of the best tools in its category. It might not have all the feature Kubernetes has, but it also has less complexity. And it definitely has all the features a small company/team needs.

        See more
        Amazon EKS logo

        Amazon EKS

        613
        340
        0
        Highly available and scalable Kubernetes service
        613
        340
        + 1
        0
        PROS OF AMAZON EKS
          Be the first to leave a pro
          CONS OF AMAZON EKS
            Be the first to leave a con

            related Amazon EKS posts

            We are looking for a centralised monitoring solution for our application deployed on Amazon EKS. We would like to monitor using metrics from Kubernetes, AWS services (NeptuneDB, AWS Elastic Load Balancing (ELB), Amazon EBS, Amazon S3, etc) and application microservice's custom metrics.

            We are expected to use around 80 microservices (not replicas). I think a total of 200-250 microservices will be there in the system with 10-12 slave nodes.

            We tried Prometheus but it looks like maintenance is a big issue. We need to manage scaling, maintaining the storage, and dealing with multiple exporters and Grafana. I felt this itself needs few dedicated resources (at least 2-3 people) to manage. Not sure if I am thinking in the correct direction. Please confirm.

            You mentioned Datadog and Sysdig charges per host. Does it charge per slave node?

            See more
            Sebastian Gębski

            Heroku was a decent choice to start a business, but at some point our platform was too big, too complex & too heterogenic, so Heroku started to be a constraint, not a benefit. First, we've started containerizing our apps with Docker to eliminate "works in my machine" syndrome & uniformize the environment setup. The first orchestration was composed with Docker Compose , but at some point it made sense to move it to Kubernetes. Fortunately, we've made a very good technical decision when starting our work with containers - all the container configuration & provisions HAD (since the beginning) to be done in code (Infrastructure as Code) - we've used Terraform & Ansible for that (correspondingly). This general trend of containerisation was accompanied by another, parallel & equally big project: migrating environments from Heroku to AWS: using Amazon EC2 , Amazon EKS, Amazon S3 & Amazon RDS.

            See more
            AWS Fargate logo

            AWS Fargate

            428
            298
            0
            Run Containers Without Managing Infrastructure
            428
            298
            + 1
            0
            PROS OF AWS FARGATE
              Be the first to leave a pro
              CONS OF AWS FARGATE
                Be the first to leave a con

                related AWS Fargate posts

                Cyril Duchon-Doris

                We build a Slack app using the Bolt framework from slack https://api.slack.com/tools/bolt, a Node.js express app. It allows us to easily implement some administration features so we can easily communicate with our backend services, and we don't have to develop any frontend app since Slack block kit will do this for us. It can act as a Chatbot or handle message actions and custom slack flows for our employees.

                This app is deployed as a microservice on Amazon EC2 Container Service with AWS Fargate. It uses very little memory (and money) and can communicate easily with our backend services. Slack is connected to this app through a ALB ( AWS Elastic Load Balancing (ELB) )

                See more
                Azure Kubernetes Service logo

                Azure Kubernetes Service

                293
                272
                0
                Simplify Kubernetes management, deployment, and operations.
                293
                272
                + 1
                0
                PROS OF AZURE KUBERNETES SERVICE
                  Be the first to leave a pro
                  CONS OF AZURE KUBERNETES SERVICE
                    Be the first to leave a con

                    related Azure Kubernetes Service posts

                    Farzad Jalali
                    Senior Software Architect at BerryWorld · | 8 upvotes · 186.4K views

                    Visual Studio Azure DevOps Azure Functions Azure Websites #Azure #AzureKeyVault #AzureAD #AzureApps

                    #Azure Cloud Since Amazon is potentially our competitor then we need a different cloud vendor, also our programmers are microsoft oriented so the choose were obviously #Azure for us.

                    Azure DevOps Because we need to be able to develop a neww pipeline into Azure environment ina few minutes.

                    Azure Kubernetes Service We already in #Azure , also need to use K8s , so let's use AKS as it's a manged Kubernetes in the #Azure

                    See more