TrustRadius: an HG Insights company

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    AWS Lambda

    Score8.3 out of 10
    N/AAWS Lambda is a serverless computing platform that lets users run code without provisioning or managing servers. With Lambda, users can run code for virtually any type of app or backend service—all with zero administration. It takes of requirements to run and scale code with high availability.

    $NaN

    Per 1 ms

    Google App Engine

    Score8.4 out of 10
    N/AGoogle App Engine is Google Cloud's platform-as-a-service offering. It features pay-per-use pricing and support for a broad array of programming languages.

    $0.05

    Per Hour Per Instance

    Kubernetes

    Score9.1 out of 10
    N/AKubernetes is an open-source container cluster manager.N/A
    Pricing
    AWS LambdaGoogle App EngineKubernetes
    Editions & Modules
    128 MB
    $0.0000000021
    Per 1 ms
    1024 MB
    $0.0000000167
    Per 1 ms
    10240 MB
    $0.0000001667
    Per 1 ms
    Starting Price
    $0.05
    Per Hour Per Instance
    Max Price
    $0.30
    Per Hour Per Instance
    No answers on this topic
    Offerings
    Pricing Offerings
    AWS LambdaGoogle App EngineKubernetes
    Free Trial
    NoNoNo
    Free/Freemium Version
    NoYesNo
    Premium Consulting/Integration Services
    NoNoNo
    Entry-level Setup FeeNo setup feeNo setup feeNo setup fee
    Additional Details
    More Pricing Information
    Community Pulse
    AWS LambdaGoogle App EngineKubernetes
    Considered Multiple Products
    Amazon AWS
    Chose AWS Lambda
    AWS Lambda is good for short running functions, and ideally in response to events within AWS. Google App Engine is a more robust environment which can have complex code running for long periods of time, and across more than one instance of hardware. Google App Engine allows for …
    Incentivized
    Chose AWS Lambda
    AWS Lambda is much easier to use than the near alternatives. It is so straightforward and lightweight it is my primary service for handling small transactions or triggers. The other services require more setup time and are more complex to use. AWS Lambda takes your code snippet …
    Incentivized
    Chose AWS Lambda
    AWS Lambda is the comparison tool to App Engine. I selected Lambda because the entire stack is basically on Amazon Web Services.
    Incentivized
    Chose AWS Lambda
    Azure Functions is another product that provides lambda functionality, but the documentation for some of Azure's products is quite hard to read. Additionally, AWS Lambda was one of the first cloud computing products on a large cloud service that implemented lambda functions, so …
    Incentivized
    Google
    Chose Google App Engine
    You can create and scale Kubernetes clusters quickly, but you have to keep an eye on that cluster. In-App Engine, you don't have to worry about infrastructure, but in some scenarios, Kubernetes fits better.
    Incentivized
    Chose Google App Engine
    You can spawn up your own cluster using Kubernetes or Container Engine which will scale automatically when configured properly, but you have to keep an eye on that cluster. In App Engine you don't have to worry about it at all, just ship your code and it will run.
    Incentivized
    Chose Google App Engine
    For our organization, we selected Google App Engine which provides a reliable and efficient way to create and deploy apps moreover it supports a lot of languages and provides automatic debugging of code which enables us to deploy code to production as soon as development is …
    Incentivized
    Chose Google App Engine
    If you have a small team which is also responsible for development of the product then surely go for it. And if you have a larger team with dedicated person to take care of deployments. Go for cheaper options such as compute engine or AWS (be sure to do your research on pricing …
    Incentivized
    Chose Google App Engine
    Azure App Service is in par with Google App Engine although you may want to use Azure App Service if you are integrating with other Microsoft IT components, for example SQL Server. Google App Engine is great when in long run, you will be using Google cloud components, for …
    Incentivized
    Chose Google App Engine
    The two giants are Google and Amazon. Both are very similar however Google App Engine allows you to deploy your web applications through platforms like Python where as if you're using AWS, you have full control on the operating system services. Google is good because you pay as …
    Incentivized
    Chose Google App Engine
    I think that Microsoft and Amazon are simply investing more in their offerings, and there are a bunch of cool PaaS solutions out there as well. Google App Engine is solid, and is probably the right choice for some projects. But ultimately one should evaluate each platform …
    Incentivized
    Kubernetes
    Chose Kubernetes
    Kubernetes is very unique. I do not think there are any competitors to take over its leading place. And you can always use Kuberntes with other tools to make the whole system better. Kubernetes is backed up by Google and has been tested over the years. It is reliable, fast, and …
    Incentivized
    Key User Insights
    Would buy again
    100%
    Would buy again
    24 Answers
    92%
    Would buy again
    12 Answers
    100%
    Would buy again
    9 Answers
    Delivers good value for the price
    96%
    Delivers good value for the price
    22 Answers
    100%
    Delivers good value for the price
    13 Answers
    100%
    Delivers good value for the price
    9 Answers
    Happy with the feature set
    100%
    Happy with the feature set
    24 Answers
    92%
    Happy with the feature set
    12 Answers
    100%
    Happy with the feature set
    9 Answers
    Lived up to sales and marketing promises
    100%
    Lived up to sales and marketing promises
    18 Answers
    100%
    Lived up to sales and marketing promises
    10 Answers
    100%
    Lived up to sales and marketing promises
    5 Answers
    Implementation went as expected
    100%
    Implementation went as expected
    21 Answers
    92%
    Implementation went as expected
    12 Answers
    75%
    Implementation went as expected
    6 Answers
    Features
    AWS LambdaGoogle App EngineKubernetes
    Access Control and Security
    Comparison of Access Control and Security features of AWS Lambda and Google App Engine and Kubernetes
    Feature
    AWS Lambda
    8.8
    7 Ratings
    4% above category average
    Google App Engine
    -
    Ratings
    Kubernetes
    -
    Ratings
    Multiple Access Permission Levels (Create, Read, Delete)8.57 Ratings00 Ratings00 Ratings
    Single Sign-On (SSO)9.03 Ratings00 Ratings00 Ratings
    Reporting & Analytics
    Comparison of Reporting & Analytics features of AWS Lambda and Google App Engine and Kubernetes
    Feature
    AWS Lambda
    4.9
    6 Ratings
    29% below category average
    Google App Engine
    -
    Ratings
    Kubernetes
    -
    Ratings
    Dashboards5.46 Ratings00 Ratings00 Ratings
    Standard reports5.05 Ratings00 Ratings00 Ratings
    Custom reports4.35 Ratings00 Ratings00 Ratings
    Function as a Service (FaaS)
    Comparison of Function as a Service (FaaS) features of AWS Lambda and Google App Engine and Kubernetes
    Feature
    AWS Lambda
    8.8
    7 Ratings
    5% above category average
    Google App Engine
    -
    Ratings
    Kubernetes
    -
    Ratings
    Programming Language Diversity9.07 Ratings00 Ratings00 Ratings
    Runtime API Authoring8.07 Ratings00 Ratings00 Ratings
    Function/Database Integration9.07 Ratings00 Ratings00 Ratings
    DevOps Stack Integration9.17 Ratings00 Ratings00 Ratings
    Platform-as-a-Service
    Comparison of Platform-as-a-Service features of AWS Lambda and Google App Engine and Kubernetes
    Feature
    AWS Lambda
    -
    Ratings
    Google App Engine
    9.5
    32 Ratings
    20% above category average
    Kubernetes
    -
    Ratings
    Ease of building user interfaces00 Ratings9.018 Ratings00 Ratings
    Scalability00 Ratings10.032 Ratings00 Ratings
    Platform management overhead00 Ratings9.032 Ratings00 Ratings
    Workflow engine capability00 Ratings8.024 Ratings00 Ratings
    Platform access control00 Ratings10.031 Ratings00 Ratings
    Services-enabled integration00 Ratings10.028 Ratings00 Ratings
    Development environment creation00 Ratings10.029 Ratings00 Ratings
    Development environment replication00 Ratings10.028 Ratings00 Ratings
    Issue monitoring and notification00 Ratings9.028 Ratings00 Ratings
    Issue recovery00 Ratings9.026 Ratings00 Ratings
    Upgrades and platform fixes00 Ratings10.029 Ratings00 Ratings
    Container Management
    Comparison of Container Management features of AWS Lambda and Google App Engine and Kubernetes
    Feature
    AWS Lambda
    -
    Ratings
    Google App Engine
    -
    Ratings
    Kubernetes
    9.2
    4 Ratings
    12% above category average
    Security and Isolation00 Ratings00 Ratings9.34 Ratings
    Container Orchestration00 Ratings00 Ratings9.84 Ratings
    Cluster Management00 Ratings00 Ratings9.84 Ratings
    Storage Management00 Ratings00 Ratings8.64 Ratings
    Resource Allocation and Optimization00 Ratings00 Ratings8.84 Ratings
    Discovery Tools00 Ratings00 Ratings9.34 Ratings
    Update Rollouts and Rollbacks00 Ratings00 Ratings9.34 Ratings
    Self-Healing and Recovery00 Ratings00 Ratings9.33 Ratings
    Analytics, Monitoring, and Logging00 Ratings00 Ratings9.14 Ratings
    Best Alternatives
    AWS LambdaGoogle App EngineKubernetes
    Small Businesses
    IBM Cloud Functions
    Score6.5 out of 10
    IBM Cloud Foundry
    Score8.5 out of 10
    Mirantis Kubernetes Engine
    Score8 out of 10
    Medium-sized Companies
    IBM Cloud Functions
    Score6.5 out of 10
    IBM Cloud Private
    Score9.6 out of 10
    Amazon Elastic Container Service (Amazon ECS)
    Score8.6 out of 10
    Enterprises
    IBM Cloud Functions
    Score6.5 out of 10
    AWS Elastic Beanstalk
    Score8.6 out of 10
    SUSE Rancher
    Score9.4 out of 10
    All AlternativesView all alternativesView all alternativesView all alternatives
    User Ratings
    AWS LambdaGoogle App EngineKubernetes
    Likelihood to Recommend
    7.5
    (52 ratings)
    9.0
    (36 ratings)
    8.7
    (19 ratings)
    Likelihood to Renew
    -
    (0 ratings)
    8.3
    (8 ratings)
    10.0
    (1 ratings)
    Usability
    8.3
    (17 ratings)
    10.0
    (8 ratings)
    9.1
    (3 ratings)
    Performance
    -
    (0 ratings)
    10.0
    (1 ratings)
    -
    (0 ratings)
    Support Rating
    8.7
    (20 ratings)
    8.4
    (12 ratings)
    -
    (0 ratings)
    Implementation Rating
    -
    (0 ratings)
    8.0
    (1 ratings)
    -
    (0 ratings)
    User Testimonials
    AWS LambdaGoogle App EngineKubernetes
    Likelihood to Recommend
    Amazon AWS
    Lambda excels at event-driven, short-lived tasks, such as processing files or building simple APIs. However, it's less ideal for long-running, computationally intensive, or applications that rely on carrying the state between jobs. Cold starts and constant load can easily balloon the costs.
    Incentivized
    Read full review
    Google
    App Engine is such a good resource for our team both internally and externally. You have complete control over your app, how it runs, when it runs, and more while Google handles the back-end, scaling, orchestration, and so on. If you are serving a tool, system, or web page, it's perfect. If you are serving something back-end, like an automation or ETL workflow, you should be a little considerate or careful with how you are structuring that job. For instance, the Standard environment in Google App Engine will present you with a resource limit for your server calls. If your operations are known to take longer than, say, 10 minutes or so, you may be better off moving to the Flexible environment (which may be a little more expensive but certainly a little more powerful and a little less limited) or even moving that workflow to something like Google Compute Engine or another managed service.
    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
    Amazon AWS
    • No provisioning required - we don't have to pay anything upfront
    • Serverless deployment - it gets executed only when request comes and we pay only for the time the request is getting executed
    • Integrates well with AWS CloudWatch triggers so it is easy to setup scheduled tasks like cron jobs
    Incentivized
    Read full review
    Google
    • Quick to develop, quick to deploy. You can be up and running on Google App Engine in no time.
    • Flexible. We use Java for some services and Node.js for others.
    • Great security features. We have been consistently impressed with the security and authentication features of Google App Engine.
    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
    Amazon AWS
    • Developing test cases for Lambda functions can be difficult. For functions that require some sort of input it can be tough to develop the proper payload and event for a test.
    • For the uninitiated, deploying functions with Infrastructure as Code tools can be a challenging undertaking.
    • Logging the output of a function feels disjointed from running the function in the console. A tighter integration with operational logging would be appreciated, perhaps being able to view function logs from the Lambda console instead of having to navigate over to CloudWatch.
    • Sometimes its difficult to determine the correct permissions needed for Lambda execution from other AWS services.
    Incentivized
    Read full review
    Google
    • There is a slight learning curve to getting used to code on Google App Engine.
    • Google Cloud Datastore is Google's NoSQL database in the cloud that your applications can use. NoSQL databases, by design, cannot give handle complex queries on the data. This means that sometimes you need to think carefully about your data structures - so that you can get the results you need in your code.
    • Setting up billing is a little annoying. It does not seem to save billing information to your account so you can re-use the same information across different Cloud projects. Each project requires you to re-enter all your billing information (if required)
    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
    Amazon AWS
    No answers on this topic
    Google
    App Engine is a solid choice for deployments to Google Cloud Platform that do not want to move entirely to a Kubernetes-based container architecture using a different Google product. For rapid prototyping of new applications and fairly straightforward web application deployments, we'll continue to leverage the capabilities that App Engine affords us.
    Incentivized
    Read full review
    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
    Amazon AWS
    I give it a seven is usability because it's AWS. Their UI's are always clunkier than the competition and their documentation is rather cumbersome. There's SO MUCH to dig through and it's a gamble if you actually end up finding the corresponding info if it will actually help. Like I said before, going to google with a specific problem is likely a better route because AWS is quite ubiquitous and chances are you're not the first to encounter the problem. That being said, using SAM (Serverless application model) and it's SAM Local environment makes running local instances of your Lambdas in dev environments painless and quite fun. Using Nodejs + Lambda + SAM Local + VS Code debugger = AWESOME.
    Incentivized
    Read full review
    Google
    I had to revisit the UI after a year of just setting up and forgetting. The UI got some improvements but the amount of navigation we have to go through to setup a new app has increased but also got easier to setup. Gemini now is integrated and make getting answers faster
    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
    Amazon AWS
    Amazon consistently provides comprehensive and easy-to-parse documentation of all AWS features and services. Most development team members find what they need with a quick internet search of the AWS documentation available online. If you need advanced support, though, you might need to engage an AWS engineer, and that could be an unexpected (or unwelcome) expense.
    Incentivized
    Read full review
    Google
    Good amount of documentation available for Google App Engine and in general there is large developer community around Google App Engine and other products it interacts with. Lastly, Google support is great in general. No issues so far with them.
    Incentivized
    Read full review
    Kubernetes
    No answers on this topic
    Alternatives Considered
    Amazon AWS
    AWS Lambda is good for short running functions, and ideally in response to events within AWS. Google App Engine is a more robust environment which can have complex code running for long periods of time, and across more than one instance of hardware. Google App Engine allows for both front-end and back-end infrastructure, while AWS Lambda is only for small back-end functions
    Incentivized
    Read full review
    Google
    We were on another much smaller cloud provider and decided to make the switch for several reasons - stability, breadth of services, and security. In reviewing options, GCP provided the best mixtures of meeting our needs while also balancing the overall cost of the service as compared to the other major players in Azure and AWS.
    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
    Amazon AWS
    • Positive - Only paying for when code is run, unlike virtual machines where you pay always regardless of processing power usage.
    • Positive - Scalability and accommodating larger amounts of demand is much cheaper. Instead of scaling up virtual machines and increasing the prices you pay for that, you are just increasing the number of times your lambda function is run.
    • Negative - Debugging/troubleshooting, and developing for lambda functions take a bit more time to get used to, and migrating code from virtual machines and normal processes to Lambda functions can take a bit of time.
    Incentivized
    Read full review
    Google
    • Effective employee adoption through ease of use.
    • Effective integration to other java based frameworks.
    • Time to market is very quick. Build, test, deploy and use.
    • The GAE Whitelist for java is an important resource to know what works and what does not. So use it. It would also be nice for Google to expand on items that are allowed on GAE platform.
    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