Good PaaS Platform with Great Support
It's one of the best serverless platforms we used so far. We created a small web application on it to use as ATS and also set up an email …
Starting at $0.05 Per Hour Per Instance
View PricingOverview
What is Google App Engine?
Google 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.
Recent Reviews
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Popular Features
- Scalability (31)9.090%
- Development environment creation (28)8.989%
- Platform access control (30)8.989%
- Platform management overhead (31)8.989%
Pricing
Starting Price
$0.05
Cloud
Per Hour Per Instance
Max Price
$0.30
Cloud
Per Hour Per Instance
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Product Demos
MapReduce Made Easy With Google App Engine
YouTube
Creating an android application with Google App Engine backend
YouTube
Features
Return to navigation
Product Details
- About
- Integrations
- Competitors
- Tech Details
- FAQs
What is Google App Engine?
Google 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.
Key Features
Popular Languages
Build applications in Node.js, Java, Ruby, C#, Go, Python, or PHP—or bring a
custom language runtime
Open & Flexible
Custom runtimes allows developers to bring any library and framework to App
Engine by supplying a Docker container
Fully Managed
A fully managed environment lets developers focus on code while App Engine
manages infrastructure concerns
Monitoring, Logging & Diagnostics
Google Stackdriver provides application diagnostics to debug and monitor the
health and performance of apps
Application Versioning
Host different versions of applications, create development, test, staging, and
production environments
Traffic Splitting
Route incoming requests to different app versions, A/B test, and do incremental
feature rollouts
Application Security
Help safeguard applications by defining access rules with App Engine firewall
and leverage managed SSL/TLS certificates* by default on a custom domain at no
additional cost
Services Ecosystem
Tap a growing ecosystem of GCP services from applications including a suite of
cloud developer tools
Google App Engine Integrations
Google App Engine Competitors
Google App Engine Technical Details
| Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Unspecified |
| Mobile Application | No |
Frequently Asked Questions
Google 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.
CloudFoundry are common alternatives for Google App Engine.
Reviewers rate Ease of building user interfaces and Scalability and Workflow engine capability highest, with a score of 9.
The most common users of Google App Engine are from Small Businesses (1-50 employees).
Comparisons
Compare with
Reviews and Ratings
(232)Attribute Ratings
Reviews
(1-5 of 5)Companies can't remove reviews or game the system. Here's why
August 18, 2019
App Engine Review!
App Engine is a fantastic service for developers who want to be able to run their code in an environment that they do not have to provision -- there is no manual server configuration or maintenance, etc, and all the developer needs to be concerned about is how their code works.
- Removes the need for manual server configuration, management, orchestration, etc
- Interfaces incredibly well with other GCP services, like Cloud Functions and Firebase
- It is not the most cost-efficient hosting provider and could continue to improve from a cost basis
- Google's UI can be confusing for newcomers when managing an App Engine deployment
96.66666666666666%
9.7
- App Engine is a great starting point for customers who are already invested or want to become further invested in the Google Cloud Platform environment
- App Engine removes the need for manual server management, which saves a lot of developer time and money
We commonly decide between App Service, Elastic Beanstalk, and App Engine. Normally, we do not have a strong preference for the services, it really comes down to whether or not there are other factors drawing us toward a particular platform. In the case of App Engine, it is a great choice for situations that leverage other Google Cloud products, like Firebase.
15
App Engine provides scalable compute resources for internet-based applications, with Google handling much of the server administration work for you. The result is that deploying, managing, and updating web infrastructure deployments is greatly simplified, leading to fewer devops cycles spent on deployment resources and more time spent on application development and quality control.
3
Part of the reason we utilize a platform like Google App Engine, or just App Engine, is to greatly reduce the resource needs for managing scalable web and application infrastructure. Rather than employ a large number of people responsible for the roll-out of infrastructure, developers can simply leverage App Engine to quickly and efficiently deploy and test their own code. As a result, very few internal resources are needed -- just a few folks with training in how App Engine's settings works is generally sufficient.
- Web Infrastructure Hosting
- Automated Scaling for Infrastructure Management
- Rapid Prototyping and Deployment
- Continuous Delivery with Automated Versioning and Rollbacks
- Easily capable of hosting more backend worker-like tasks, not just web-facing applications
- Rapid prototyping of new types of applications
- We'd like to take advantage of some of the other platforms that App Engine supports, having been mainly focused on Python development
- We'd like to see better support for Java EE and Spring, as some of the functionality that we like to implement often involves complicated workarounds to deal with how App Engine generally behaves
August 16, 2019
Expensive, Cutting Edge and Highly Recommended
We use Google App Engine for content distribution of digital publishing assets as well as analytics and authentication services for a wide array of platforms. The whole organization uses Google App Engine in some capacity or another. The business problems it addresses are virtualizing services and abstracting away server configuration, load balancing, software updates and everything else we would have to do to set up the same infrastructure on a classic web server stack. Google App Engine has expedited our development and deployment processes tremendously so we can continue innovating with new services, getting them up and running quickly, while trusting that our existing services are running on a rock solid cloud platform backend.
- 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.
- Documentation does not always keep up with the latest changes to the service. Google App Engine has undergone a lot of changes these past couple of years. At times, we were surprised to find out that something we didn't think was possible was, or, conversely, something that was supposed to work fine which had been deprecated. We also ended up using some undocumented features and weren't sure whether they would keep working or not.
- Price. Google App Engine isn't cheap. But, you get what you pay for. Rock solid service, great tools, at a hefty price.
- Difficult to tell how to optimize costs. We racked up the expenses and it is still a mystery where all the costs are being incurred.
- Some intimidating or arcane aspects of configuration. Most of it was a breeze but every now and then something would be pretty far out and require a few of us developers putting our heads together to figure it out.
- Sometimes required reading source code to figure out how to do something. Not a ton of examples of how to do various things, nor Stack Overflow posts, at least in the beginning. I imagine this will change as the community grows. But sometimes it felt like we were all alone trying to figure out how to do things.
43.63636363636363%
4.4
- Positive impact: Google App Engine let us rapidly build and deploy web services which support an array of applications across mobile and web platforms. We have found the services to be highly reliable and have been overall very satisfied with the level of stability, security and functionality we've achieved.
- Negative impact: We are dissatisfied with the seemingly-unnecessary level of complexity in some areas which has made code hand-off difficult. It has taken developers many months to learn the ins and outs of Google App Engine and understand the complex infrastructure of our services and so when someone has never worked on these services before, there can be a sizable ramp up time. So while it was very quick to build, it is not always obvious or apparent how to make modifications or how everything works together. There is a bit of "magic" involved where you have to really understand the system to see why, counter-intuitively, certain things happen the way they do.
- Positive impact: We've had the flexibility to implement certain features which we thought would be unsupported or too difficult to achieve with Google App Engine. So it has allowed us to do some very cool things that we were surprised were possible.
- Negative impact: It's very expensive, and combined with the extra time spent in development trying to figure out some of the more arcane aspects of Google App Engine, it is hard to know whether we could have saved money by choosing a different platform provider, but it seems likely.
AWS and Heroku are both great, and I use them both extensively for different projects. Google App Engine was chosen because it is much more innovative than AWS, and because Heroku specializes in Ruby on Rails. Even though Heroku supports Java and other services, we feel Google App Engine is much more robust than Heroku, and simply more technologically advanced (modern, using contemporary/cutting edge technology) than AWS.
3
Our software development team uses Google App Engine for web services that we provide to customers, such as analytics, cloud conversion for digital publishing, and secure file storage. We use Google App Engine because it allows us to rapidly develop and deploy web services without a lot of configuration, and because we are able to test the services locally, then deploy them knowing that they will operate in exactly the same way as our local environments.
3
Our software team keeps up to date with Google App Engine and is ready to go to fix problems as they arise. The skills involved in supporting Google App Engine are essentially being able to keep up to date with the documentation and be familiar with the best practices and design concepts employed by Google for this service.
- Authenticated, secure file storage and distribution
- Rapid deployment of web services
- Computational power for batch file conversion
- We were able to use the Google App Engine file storage to perform many security functions without having to add new features on another layer.
- We hope to continue using Google App Engine for future web services and computational workload tasks.
August 15, 2019
Google App Engine's best feature is cloud endpoint
We are currently evaluating Google App engine as a platform as a service to our customers. The Google App Engine cloud endpoints is equivalent to Microsoft Azure's web apps or API apps. We are impressed with its ability to deploy Java or Python based RestFul API directly to Cloud endpoints. I coded the logic in the RestFul API to access Google's Cloud DataStore (kind-entity-property type of data store). Google's SDK made it easy to integrate its App Engine with its storage solutions. I have not tried its Cloud Bigtable from Cloud endpoints but I'm sure it's on our next task list.
Google App Engine's primary programming language is Java. I tried JetBrain's IntelliJ IDEA for managing Google App engine cloud endpoint projects. I used the community edition, which had less support for Google App Engine Cloud endpoint. The enterprise edition should have better support.
For those who prefer to use Python, JetBrains may have just released PyCharm for $99. Nothing comes for free. If you work at a company that has those licenses, you should feel lucky. Having a good IDE is critical to productivity. It has a "PyCharm Free Educational (Classroom) License" for free.
- Auto scale application load.
- Platform as a Service feature abstracts the web server layer.
- Perfect for Android or iOS app server logic development.
- Connect to different Google storage types.
- Able to use C# as the programming language in its SDK.
- Integration with Visual studio C# for using Google app engine cloud endpoint SDK.
- Documentation on choosing a IDE to get started. Doing things in the command line is too basic. It's good to know them but having a sophisticated IDE is the next step to achieve higher productivity.
91.81818181818181%
9.2
- Positive: Customers with Java, Python code base may choose to use Google app engine over Microsoft Azure for deploying their web applications.
- Negative: Customers with C# ASP.NET web application code base may choose not to use Google app engine due to lack of C# support in the SDK.
- Positive: pricing is 10% more competitive compared to Microsoft Azure and %48 more competitive compared to Amazon AWS.
- Windows Azure
Compared with Microsoft Azure, Google App Engine requires a more complicated development environment setup. It's not as simple as using Visual Studio 2015 with Azure SDK. There are multiple IDE on the market to choose from for developing apps for Google App Engine. JetBrains may have the best IDE.
Consider the data store your web applications will need. If it's a brand new v1 application, look at the storage offerings from Microsoft Azure, Amazon, Google. It's quite difficult to connect to Amazon's or Microsoft Azure's storage from web applications running in Google App Engine.
Consider the data store your web applications will need. If it's a brand new v1 application, look at the storage offerings from Microsoft Azure, Amazon, Google. It's quite difficult to connect to Amazon's or Microsoft Azure's storage from web applications running in Google App Engine.
75
- serving micro-services based REST APIs
- corporate inventory management Web applications
- store based web applications
- payment processing REST APIs
- Product catalog REST APIs
- Order management REST APIs
- Store Location management REST APIs
9
- Language runtime specific knowledge and skills
- For App Engine flexible, skills and knowledge of Docker containers
- StackDriver monitoring for configuring real time alerts to the DevOps team.
- Trackdriver trace to troubleshoot service level latency.
- Stackdriver Debug and error reporting to find production bugs.
- Stackdriver profiler to get application performance insights.
- Stackdriver logging to troubleshoot general application errors and warnings.
- Google Cloud certified professional cloud developer.
- DevOps team. Ops team are lesser qualified because troubleshooting App Engine errors will require most developer's skills.
- building new Microservices
- building new REST APIs
- rebuilding or migrating existing microservices to App Engine
- rebuilding or rehosting containerized web apps to App Engine flexible.
- Migrate low security risk REST API to App Engine
- configure Serverless VPC Access for App Engine standard services to consume Cloud SQL or Compute engine hosted microservices or databases.
- Use App Engine firewall to restrict traffic into the deployed services.
- Migrate existing Java 8 App Engine standard services to Java 11 with Google Cloud SDK.
- Build greenfield Java 11 REST APIs with App Engine standard Java 11 runtime.
October 09, 2015
Good App Engine (GAE)
The Google App Engine solution is helping an entirely new category of applications that process data in real-time and at scale very robustly. It has faster, easier, more detailed simulations and solutions for all cloud related requirements. We use Google App Engine to develop and deploy both internal and public web applications. The APIs for accessing the datastore are very easy to use.
- The APIs for accessing the datastore are very easy to use.
- Implementing text indexing and search related applications perform better on Google App Engine compared to other app engines.
- Reliable NoSQL datastore, including atomic transactions and a query engine.
- Developers have read-only access to the filesystem on Google App Engine.
- Google App Engine limits the maximum rows returned from an entity get to 1000 rows per Datastore call.
- Not suitable for CPU intensive calculations.
72.72727272727272%
7.3
- Increased employee efficiency.
- Less infrastructure maintenance time.
- Amazon Elastic Compute Cloud (EC2)
The immediate benefits of Google App Engine is that it is essentially maintenance free as it relates to infrastructure (scalable web server and database administration). Google App Engine is more tailored to those developers that only want to focus on their applications and not the underlying system. In a way you can consider that developer friendly.
5
They simplify the customer management information that was distributed in multiple systems across its sales and marketing organization.they design, develop and implement a system that consolidated all the information to a single point data source for other customer sensitive data, including the CRM system.
2
Technical Engineers.
- Data analysis
- web app deployment
- app deployment through ansible
- docker installation
- data algorrithm processing. data intensive operation
No
- Product Features
- Product Usability
- Analyst Reports
More robust and scalability.
- Don't know
No
- pricing
Yes
No
Regarding the application deployment support.
- deployment
- scalability
- ease of use
- multi platform support
- memory intensive operations
Use is based on client or project needs. It is used mainly as a cloud based API service so that corporate enterprise systems can leverage it internally or with other service dependent applications.
- Cloud based RESTful APIs
- Access to big data resources for reporting and analytics
- Custom Cloud web hosted applications
- Cost, speed, ease of adoption
- Implemented a custom company based web site using Vosao on GAE CMS
- Administration and management - more Azure like portal
- Better reporting on forecasted and actual usage via notifications.
- Better documentation, examples. More use case centric documentation.
- 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.
- Amazon Web Services,Microsoft Azure
- These products really only intersect with a small footprint.
- Azure is closest to what GAE provides as a PaaS
- Azure is certainly making greater 'in-roads' on the enterprise cloud adoption side of the business. Google has still work to do to come close to Microsoft's ability to adapt for the enterprise
- Now that GAE supports PHP, Python, Java and Go - it needs to expand its language use, such as C#, Ruby and others if it is to stay competitive in the market
3
Project execution development
1
- Needs a good understanding of cloud based management
- Understands GAE and some aspects of tuning for use case used.
- Understands how to improvise a design for better GAE usage
- Published cloud APIs
- Published low maintenance web applications
- Demonstration of how easy cloud based development can be
- Demonstrates integration to other Google products and services
- Photo sharing
- Live sports stats collection, collation and reporting
- API usage
- Verification and validation services
- APIs
- Security frameworks
No
- Price
- Product Features
- Product Usability
- Product Reputation
- Vendor Reputation
Product Usability is off the charts. More advanced usage is where it starts to get a little tricky
Well that all really depends on the client needs in my business. If they are a java/python shop then it is a start for GAE usage. If the client is willing or potentially needs integration to other Google products and services then that is also a plus. It all depends on the client needs, aspirations and current skill sets.