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.
$0.05
Per Hour Per Instance
ServiceNow App Engine
Score 7.4 out of 10
N/A
ServiceNow App Engine aims to bring creator workflow apps to production quickly for mission-critical tasks. Design with best-practice guidance and templates within a holistic low-code dev experience.
N/A
Pricing
Google App Engine
ServiceNow App Engine
Editions & Modules
Starting Price
$0.05
Per Hour Per Instance
Max Price
$0.30
Per Hour Per Instance
No answers on this topic
Offerings
Pricing Offerings
Google App Engine
ServiceNow App Engine
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Google App Engine
ServiceNow App Engine
Features
Google App Engine
ServiceNow App Engine
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
Google App Engine
8.7
31 Ratings
10% above category average
ServiceNow App Engine
-
Ratings
Ease of building user interfaces
9.017 Ratings
00 Ratings
Scalability
9.031 Ratings
00 Ratings
Platform management overhead
9.031 Ratings
00 Ratings
Workflow engine capability
9.023 Ratings
00 Ratings
Platform access control
9.030 Ratings
00 Ratings
Services-enabled integration
8.027 Ratings
00 Ratings
Development environment creation
9.028 Ratings
00 Ratings
Development environment replication
8.027 Ratings
00 Ratings
Issue monitoring and notification
9.027 Ratings
00 Ratings
Issue recovery
9.025 Ratings
00 Ratings
Upgrades and platform fixes
8.028 Ratings
00 Ratings
Low-Code Development
Comparison of Low-Code Development features of Product A and Product B
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.
When the solution involved complex workflows and integration with many 3rd party applications, we felt the Now app engine was less appropriate as it could not handle different integrations simultaneously for incident resolution and complaints management. This was well suited and managed by people who don't know basic coding.
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)
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.
Google App Engine is very intuitive. It has the common programming language most would use. Google is a dependable name and I have not had issues with their servers being down....ever. You can safely use their service and store your data on their servers without worrying about downtime or loss of data.
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.
App engine can be used just to process the minimal amount of the data which is being received from the user. We are service now catalogue items or any other data technology.
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.
ServiceNow App Engine is best among all the competitors. Its integration is best with Outlook and ERP, its SLA management is best, and very organized filters are very useful. Categorization of tickets is something that is very useful. It's very easy to search the tasks/order with limited keywords and very easy to customize. The best part is we can simply reply on mails using ServiceNow App Engine and keep a proper log of the tickets.
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.