TrustRadius Insights for Google App Engine are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Efficient Email Servers: Users have praised the email servers for their efficiency in delivering messages promptly, ensuring reliable communication.
Easy Data Upload: Many users find the ability to upload data to web applications effortlessly as a valuable feature that enhances their overall user experience.
Automatic Scaling of Apps: The automatic scaling of apps based on user demand is highlighted by users as a beneficial feature that ensures smooth performance even with increasing usage.
Various Programming Language Support: Users appreciate the platform's support for programming languages like Java, Python, Php, and Ruby, which facilitates development and adds flexibility.
Straightforward Billing System: The straightforward and easy-to-understand billing system provided by Google is appreciated by users for simplifying financial management within the platform.
Project-Based Resource Management: The project-based management of resources by Google is seen as a beneficial feature that contributes to efficient resource allocation and utilization.
Flexibility in Scaling Instances: Users value the ability to scale instances up or down based on business needs, allowing effective demand response while optimizing costs.
Managing Server-less Resources Efficiently: The ease of managing server-less resources and deploying applications efficiently is highlighted as a key strength of the platform.
Cost-Effective Solution for Small Applications: Google App Engine is recognized as a cost-effective and time-saving alternative for running small applications, enabling quick implementation.
Loading Reviews List....
Google App Engine Reviews
12 Reviews
Professional, Scientific, and Technical ServicesLegal Services1Information Technology & Services10Management Consulting1
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 server which worked very well with good performance and minimal administration. Their support team is superb as they addressed our queries so effectively and fast. It's also very good in terms of integration with other applications and existing infrastructure.
Pros
Email servers are good with email delivery in inbox.
It enables uploading data to web applications.
We're able to manage multiple applications with a single dashboard which has a great UI.
Cons
Some more documentation and tutorials would help a lot.
I would like to see integration with more open source applications.
I would like more options to choose different UI themes.
Likelihood to Recommend
Google App Engine is a great platform to cater to the needs of different size organizations from small businesses to enterprise levels. Due to its great support and the large community, it can be deployed with minimum administration. It is also a great choice for businesses requiring an extra level of security.
We're using Google App Engine to build and host our web application and backend across the organization. This helps us in building a highly scalable applications on a fully managed server-less platform.
Pros
It's very simple to integrate in the application.
Provides deployment history, so that you can switch back to any instance.
Fully scalable, so that you can add power as needed.
Cons
They can improve on their documentation.
Navigation can be made more simple.
Pricing can be reduced.
Likelihood to Recommend
The fact that it is very easy to understand for a person who is making his/her first step into cloud technology. Auto scalable and managed totally by Google is also a great feature for a small team or a prototype application. So, if you want to get a system up and running quickly then this can be really handy.
VU
Verified User
Engineer in Information Technology (Information Technology and Services company, 51-200 employees)
We deployed Moodle(LMS) and Odoo(ERP) applications on Google App Engine using Marketplace available configurations from Bitmani. We are using App Engine to host such client applications. The Google Marketplace saved us many hours of trying to configure these large applications ourselves.
Pros
Google's Marketplace is a great resource. I did not find this on other cloud services.
Google's billing system is easy and straightforward to understand.
Google's project based management of resources is good.
Cons
Google dashboard is not so helpful. It does not give a summary of the resource like in AWS.
Google console should have something like "Recently visited services" of AWS.
It is hard to install Google Cloud SDK.
Likelihood to Recommend
Google App Engine is great for Kubernetes, since it's very stable and new releases come quickly. Google Marketplace saved a lot of time if standard open sources applications like Moodle has to be deployed and tested quickly. Google App Engine is not good for beginners in cloud hosting, since it's hard to configure.
We use Google App Engine to house many of our mission-critical web applications with zero downtime. It solves the need to have 100% uptime with no added long term equipment costs and additional IT support staff.
Pros
Ease to deploy.
Flexible ability to scale to meet increases in users.
Ability to program in various languages allowing for different development teams to work with it.
Cons
The ability to only run web applications. If it could also run self-executing non-web based applications it could be used more heavily.
It only allows the use of the Google Cloud store which limits the ability to use other cloud stores already in use in the enterprise.
It's a closed API that can lock into being dependent entirely on Google. There are many open-source projects ongoing that can help to alleviate.
Likelihood to Recommend
If there is a need to deploy a web application on new equipment without purchasing hardware and requiring additional IT support, then App Engine will fit the need. The pricing is low and can be scaled to meet the needs.
VU
Verified User
Manager in Engineering (Information Technology and Services company, 1001-5000 employees)
Missing scheduler as a service. Has static cron, but no fault-tolerant, dynamic scheduling as a service. Azure has this.
Documentation. Documentation can be stale, to terse, cumbersome to navigate.
Deploy time and CI. Azure has Git hooks and auto update built in. So from commit to live can be under one minute. GCP more manual, and closer to 5+ min for same.
Likelihood to Recommend
Well suited: Prototype. Test. App scale. Small team.
Less well suited. When higher (more granular) level of control is needed, AWS is still superior.
It serves all our traffic to end users, which is basically one of the most important things for our organization.
Pros
Serving traffic to end users. It can scale automatically when traffic spikes.
The standard environment has some limitations, but it encourages you to write "scalable" code.
With Flexible Environment, you can serve any Docker container you want, still taking advantage of auto scaling.
Easy integration with other Google Cloud products, e.g. Datastore, Pub/Sub, Cloud Storage, etc.
Cons
Flexible environment needs scaling to zero and support for all APIs available in Standard Environment like ndb for Python and Task Queue.
Standard Environment needs to update some outdated libraries like lxml for Python.
Instance pricing of Standard Environment could be lowered, since it wasn't updated for many years.
Likelihood to Recommend
It's a good use case to use App Engine when you need to serve traffic to large amount of users, but you should avoid doing any computation on it. It's better to use Compute Engine or Dataflow to process your data. It has a free tier so it's very useful for non-yet-existing startups.
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.
Pros
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.
Cons
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.
Likelihood to Recommend
What kind of data store do you plan to use for your server side application? Make sure Google App Engine SDK supports them.
Will your server applications be REST based? Think about using cloud endpoint.
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.
Pros
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.
Cons
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.
Likelihood to Recommend
Google App Engine's infrastructure removes many of the system administration and development challenges of building applications to scale to millions of hits. Google handles deploying code to a cluster, monitoring, failover, and launching application instances as necessary.
VU
Verified User
Engineer in Engineering (Information Technology and Services company, 1001-5000 employees)
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.
Pros
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
Cons
Administration and management - more Azure like portal
Better reporting on forecasted and actual usage via notifications.
Better documentation, examples. More use case centric documentation.
Likelihood to Recommend
Learning curve is relatively short.
Integration to Eclipse is awesome.
Integration with standard frameworks is getting better - I would not recommend loading entire spring framework on it, but aspects of it are more useful.
App Engine allows organizations to leverage the Google Apps APIs and get easy access to some functionality that is not available the standard Google Apps users. For example, the ability to maintain your user's meta data, such as their business title, department, work address, work phone number, cell phone number etc. These are not available in the Google Apps Control Panel, but with some coding on Google App Engine, you can create the interface that allows users to self-manage their own meta data. This just one example of leveraging Google App Engine to complement a Google Apps rollout.
Pros
Building an application that uses Google's Authentication, means users no longer need to remember an different user id and password. Once they are logged into to Google, they can seamlessly access your application hosted on Google App Engine.
Google App Engine automatically scales up and down. SO if your application receives a spike in user traffic, App Engine automatically launches additional instances of your application to cater for the increased traffic. Once App Engine detects that the spike is usage is over, it automatically scales down to handle the current traffic.
Google App Engine can be easily integrated with Google Cloud SQL, Google Compute Engine, Google Cloud Storage etc, so that you can build out a full application using one or more of Google's Cloud Platform products.
Cons
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)
Likelihood to Recommend
App Engine is well suited for most web applications, especially when you are unsure about the amount of traffic you are expecting to have. Knowing that App Engine will scale up and down automatically gives you a peace of mind that your application will not crash if demand suddenly increases! And you don't need to worry about paying for a high end solution with redundancy and load balancing built in - as App Engine handles all of that - and you only pay for the resources you actually use.
VU
Verified User
Consultant in Research & Development (Information Technology and Services company, 51-200 employees)