Google App Engine vs Google Cloud Functions

Need advice about which tool to choose?Ask the StackShare community!

Google App Engine

7.4K
5.7K
+ 1
612
Google Cloud Functions

397
389
+ 1
20
Add tool

Google App Engine vs Google Cloud Functions: What are the differences?

Developers describe Google App Engine as "Build web applications on the same scalable systems that power Google applications". 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. On the other hand, Google Cloud Functions is detailed as "A serverless environment to build and connect cloud services". Construct applications from bite-sized business logic billed to the nearest 100 milliseconds, only while your code is running.

Google App Engine and Google Cloud Functions are primarily classified as "Platform as a Service" and "Serverless / Task Processing" tools respectively.

"Easy to deploy" is the primary reason why developers consider Google App Engine over the competitors, whereas "Serverless Applications" was stated as the key factor in picking Google Cloud Functions.

Snapchat, Accenture, and Movielala are some of the popular companies that use Google App Engine, whereas Google Cloud Functions is used by Kalibrr, Policygenius, and BetterCloud. Google App Engine has a broader approval, being mentioned in 482 company stacks & 345 developers stacks; compared to Google Cloud Functions, which is listed in 55 company stacks and 21 developer stacks.

Advice on Google App Engine and Google Cloud Functions

What are the best options to host a Spring Boot application that acts as a receiver and publisher from Google Cloud Pub/Sub. I am using Google App Engine to do that, but there is Google Cloud Dataflow and Google Cloud Run that can be used. Which is the best option that can be used for this purpose and also that can handle the failover scenarios as well. Thanks!

See more
Replies (2)
Stephen Fox
Artificial Intelligence Fellow · | 3 upvotes · 1.6K views

You should probably stick with App Engine Standard, if you need customization of some sort and your app needs to do more than just Pub/Sub. If all you're doing is short processing of messages (e.g. pub/sub + writing to a data store), use Cloud Run.

Google Cloud offers the continuum from fully managed to fully manual infrastructure, so it really depends on how much control you want to hand over versus getting things done for you. I've engaged with teams that really just needed App Engine, but were reinventing it with Compute Engine because they didn't know better. Others were trying to use Cloud Functions for the job of Cloud Run. Trust the docs and you'll prosper.

See more
Recommends

This is an major concerning topic for discussion. For any applications to do something with the data, first have to decrypt it. Creating a potential window of opportunity for hackers. For this I have been using Daton's Google Cloud Storage

See more
Decisions about Google App Engine and Google Cloud Functions
Clifford Crerar
Software Engineer at Bidvest Advisory Services · | 9 upvotes · 37.5K views

Run cloud service containers instead of cloud-native services

  • Running containers means that your microservices are not "cooked" into a cloud provider's architecture.
  • Moving from one cloud to the next means that you simply spin up new instances of your containers in the new cloud using that cloud's container service.
  • Start redirecting your traffic to the new resources.
  • Turn off the containers in the cloud you migrated from.
See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Google App Engine
Pros of Google Cloud Functions
  • 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
  • 6
    Serverless Applications
  • 4
    Its not AWS
  • 3
    Simplicity
  • 2
    Free Tiers and Trainging
  • 1
    Typescript Support
  • 1
    Customer Support
  • 1
    Blaze, pay as you go
  • 1
    Simple config with GitLab CI/CD
  • 1
    Built-in Webhook trigger

Sign up to add or upvote prosMake informed product decisions

Cons of Google App Engine
Cons of Google Cloud Functions
    Be the first to leave a con
    • 1
      Node.js only
    • 0
      Typescript Support
    • 0
      Blaze, pay as you go
    • 0
      Simple config with GitLab CI/CD

    Sign up to add or upvote consMake informed product decisions

    What is 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.

    What is Google Cloud Functions?

    Construct applications from bite-sized business logic billed to the nearest 100 milliseconds, only while your code is running

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Google App Engine?
    What companies use Google Cloud Functions?
    See which teams inside your own company are using Google App Engine or Google Cloud Functions.
    Sign up for Private StackShareLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Google App Engine?
    What tools integrate with Google Cloud Functions?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to Google App Engine and Google Cloud Functions?
    Heroku
    Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling.
    Amazon Web Services
    It provides on-demand cloud computing platforms to individuals, companies and governments. It offers reliable, scalable, and inexpensive cloud computing services.
    DigitalOcean
    We take the complexities out of cloud hosting by offering blazing fast, on-demand SSD cloud servers, straightforward pricing, a simple API, and an easy-to-use control panel.
    AWS Lambda
    AWS Lambda is a compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security.
    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.
    See all alternatives