TrustRadius
Google's platform-as-a-service offering.https://dudodiprj2sv7.cloudfront.net/product-logos/sh/S2/IT1Q2MLGA9B6.PNGGoogleApp Engine Review!2018-08-20T19:36:35.509ZApp 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,9,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,AWS Elastic Beanstalk,AWS Elastic BeanstalkJoshua DicksonGCP hits the nail on the head. (Sometimes)2018-04-13T19:02:28.525Z[It's being used for] Testing across various departments (Skunkworks. POCs, including Apigee API Gateway).,Client SDK and examples for integrating with services (Datastore/Storage/Pub/Sub).
Lightweight deployment code/config (lightweight YAML).
Autoscale (configuration and runtime).
Flexible runtimes.,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.,9,Save time
Save resources
Near effortless scaling,,SAP BusinessObjects BI Platform, Oracle Application Express, Joyent TritonRobert ChristianSolid solution, maybe not as great as the competition2018-08-02T17:31:28.997ZWe developed and deployed a basic app via Google App Engine in order to evaluate their serverless architecture. Development and deployment were mostly pain free, and we were able to quickly go live with a scalable solution where we didn't have to worry about infrastructure, using the language of our choice (many are supported).,Supports all popular languages (and you can even bring your own language runtime)
Built-in automatic scaling is great,Lags behind competing platforms (Azure, AWS) in terms of features
Less documentation, examples, etc. as compared to competitors' platforms,7,Easy enough to get up and running; speedy prototyping and deployment which saved us time and money
Automatic scaling meant for less issues after going live,Microsoft Azure, AWS Lambda, AWS Elastic Beanstalk and Heroku,Freshdesk, Zenefits, Zendesk, GustoVerified UserExpensive, Cutting Edge and Highly Recommended2017-04-25T20:27:30.699ZWe 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.,10,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.,Amazon Web Services and Heroku,Microsoft Office 365, Dropbox, Box, Google DriveJonah DempcyUsing Google App Engine to build a classic Java Spring MVC application2017-04-18T16:11:51.103ZGoogle App Engine (GAE) is the core engine for a specialized web application in-house product. The web application allows the sales department staff to produce reporting, follow up regarding multiple deposit amounts, do the link between Google Drive (as a hosting cloud) and electronic signatures of clients. The web app is also responsible for the "after sales" process and also allows us to maintain the customers' database.,Well suited for doing asynchronous long running process jobs through task queues
Supports for huge files upload process (fast and efficient)
Integrates pretty well with Java and Spring MVC technologies,Although GAE does support relational databases if you pay for it, developers wanting to try GAE for free are forced to use cloud datastore which is a NoSQL database.
Logging is recorded and accessible through a web console. However, there is no easy way (I mean through the console) to display a custom log line format like it's possible with slf4j or log4j logging patterns. This makes reading log inefficient.
The GAE plugins for Eclipse are buggy and inconsistent. Many times we are forced to reboot the local server after a full webapp recompile, and the command line SDK is not intuitive.,7,For a small enterprise with appropriate software engineer the ROI is excellent because the cost of GAE usage is very low compare to the quatity of information it can process in a day to day basis.
GAE allows custom powerful API usage but this can be a double-edged sword because you are binding your application with this particular product.,Amazon Web Services,Google DriveAndre Masson
Unspecified
Google App Engine
133 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
