Try our new research platform with insights from 80,000+ expert users
PeerSpot user
Principal Consultant/VP of Technology
Vendor
Easy to upload from IDE. ...

What is most valuable?

Easy to upload from IDE.

What needs improvement?

Need a better documentation and tech support.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user7629 - PeerSpot reviewer
Consultant with 51-200 employees
Vendor
3 reasons I would choose to use AppEngine

There are 3 reasons I would choose to use AppEngine
1. Software is super simple and working with servers in the future is a no go.
2. Software is going to have 100+ millions users overnight. Will still need to be tweaked and optimized to handle the traffic on AppEngine. I have never seen anyone with this crystal ball but who knows you may have one.
3. Google integration is at the core of the software. AppEngine is really easy to do things like authentication with a Google account. Using Google storage or say the Google SQL service would greatly benefit from the software running inside the Google network.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Google App Engine
October 2024
Learn what your peers think about Google App Engine. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,649 professionals have used our research since 2012.
it_user7533 - PeerSpot reviewer
Developer at a tech vendor with 51-200 employees
Real User
The hidden cost of Google App Engine

Google App Engine's pricing model costs me way more than the small amount of money I'm charged every week. It costs hours of time.

Now what do I mean by that. I love App Engine and use it every day, there is currently no faster way to get an experiment up and running. The pricing model sounds great: Pay only for what you use. But without realizing, that this model can take giant tolls on development time, it will. At least if you have to care about money.

The problem develops as follows:

1. You have a great new feature to implement.
2. You design a rough implementation, that will get it working asap.
3. You notice a few unnecessary datastore/bandwith/cpu calls/bytes/hours (which AppEngine charges for), that might cost you thousands, if the first few million users hit your site on launch day...
4. But no worries, this can be solved with a slightly redesigned data-model. Go back to 2.

All the momentum you can build up with GAE (setting up a new project in about 5 minutes) can be destroyed in this vicious circle.

Maybe this is common knowledge, but if you are like me, try this:
Ignore everything you know about GAE optimizations and get your feature implemented.
If, one day, millions of people should hit on your site, be happy, pay a higher bill that month and start optimizing.

This should apply to a lot of "Pay as you go" - models out there.

Again, maybe this is just me learning obvious stuff, but this mindset saved me hours, and saving time is great.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
IT Manager Assistant at Aras
Real User
Good product functionality with an easy, simple setup process
Pros and Cons
  • "The WhatApp feature is the most valuable."
  • "I am limited to sending a photo to five people. I want to be able to send a photo to many people, not just five."

What is our primary use case?

We are using this application for learning purposes.

How has it helped my organization?

It helps with my work and my customers.

What is most valuable?

The WhatApp feature is the most valuable.

The functional is good.

What needs improvement?

I am limited to sending a photo to five people. I want to be able to send a photo to many people, not just five.

For how long have I used the solution?

I have been using the solution for about three years.

What do I think about the stability of the solution?

It is stable.

What do I think about the scalability of the solution?

We have one user on the app (me). I can download the app on my phone.

I plan to use the app more in the future.

How are customer service and technical support?

The technical support is good enough.

Which solution did I use previously and why did I switch?

I have not used another solution previous to this.

How was the initial setup?

The initial setup is simple and easy.

The deployment and implementation did not take a long time.

What about the implementation team?

The deployment was done in-house. I deployed it. I maintain it now.

What's my experience with pricing, setup cost, and licensing?

I would like to have more free application with it. Some of the applications, I am paying more for them. I think that they must be free.

Which other solutions did I evaluate?

I did not consider another solution.

What other advice do I have?

I have found it useful in my work and life.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
DirectorManaging Partner at a tech services company with 11-50 employees
Real User
Effective self-management and implementation is straightforward
Pros and Cons
  • "Google App Engine's most valuable feature is self-management. You do not have to manage the infrastructure underneath where all the functions are happening, such as load balancing deployment and version management, they are managed by the system itself."
  • "The only concern is that there is a number of the offerings which are built on their own proprietary technologies. With some of the offerings in Google Cloud, it's difficult to have a path to migrate to other cloud providers."

What is our primary use case?

We have five Google App Engine applications deployed on private clouds, and we have some deployed on public clouds. We use both Google and Microsoft.

What is most valuable?

Google App Engine's most valuable feature is self-management. You do not have to manage the infrastructure underneath where all the functions are happening, such as load balancing deployment and version management, they are managed by the system itself.

Google Cloud has a number of products that complement each other in being able to provide solid cloud feature sets. We've had many products that are available on Google Cloud and you are able to build whatever you want. There's always a solution for what you need.

What needs improvement?

The only concern is that there is a number of the offerings which are built on their own proprietary technologies. With some of the offerings in Google Cloud, it's difficult to have a path to migrate to other cloud providers.

For how long have I used the solution?

I have been Google App Engine for approximately four years.

How was the initial setup?

The solution is easy to deploy. 

What other advice do I have?

I rate Google App Engine an eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user1158 - PeerSpot reviewer
Developer at a tech company with 51-200 employees
Vendor
Overall a good and cheap platform with scalability support. Good for individuals and startups, but not suitable for heavy/large applications.

Valuable Features:

- A very good platform for those applications that store something and retrieve it back. - Google takes care of deploying the code to the clusters, monitoring, failover, and launching application instances as and when necessary. This takes a lot of the administrative work off the user. - Easy and cheaper (in the short term) - Unlimited scalabity to your application, and scales with demand. - GAE supports MySQL db as well. - App Engine doesn't provide you with the flexibility to use an equivalent service if you need to pick something else for your app.

Room for Improvement:

- Developers have read-only access to the filesystem on the Google App Engine. - GAE is not suitable for CPU intensive calculations. - You cannot produce a social graph using Google app engine. - Once you think of migrating out of the AppEngine world, you'll face a lot of problems. For example, having to change your code to use your own datastore, task queues, and other services. If your application is fairly large, this will be a very difficult process. - Since the backend is completely manage by Google, you don't have control over the environment your application runs in. - Apart from the free space and to build some "Hobby" websites, Google App Engine is not the place java guys should look in as Java is quite heavy on memory front.

Other Advice:

Overall a good platform for running small applications that basically deals with storing and retrieving data from backend. Since the backend is handled by Google, you get a scalable app platform, but at the cost of losing control over the backend environment. You cannot tweak the backend and you just have to leave with whatever Google has to offer.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user3876 - PeerSpot reviewer
it_user3876Database Manager at a tech company with 51-200 employees
Vendor

There are a number of reasons that make GAE a good choice including automatic scaling, easy to code and setup configuration files and a pre-configured architecture that makes application development easier.

See all 2 comments
it_user981 - PeerSpot reviewer
Manager of Development at a tech company with 51-200 employees
Vendor
A good application hosting option for short term, low budget startups

Valuable Features:

Zero maintenance cost for web servers Reliable for scalability Free basic account with limited quota for trial Suitable for startups with limited users and limited resources

Room for Improvement:

No filesystem access More expensive than the alternate options if a product/service has a lot of users Language support limited to Java and Python Database options limited to MySQL and Google data store

Other Advice:

I have been using it for a startup for over an year. Initially it was great, but with an expanding user base, it makes more sense to host my own servers.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user82776 - PeerSpot reviewer
it_user82776Chief Executive Officer at a tech services company with 1,001-5,000 employees
Consultant

I think having 5 developers working with you to allow for patching upgrade and zeroing down on scalability, and yes having your own server will help the effects of over expanding customer base. Like the Khan Academy did.

See all 2 comments
Buyer's Guide
Download our free Google App Engine Report and get advice and tips from experienced pros sharing their opinions.
Updated: October 2024
Product Categories
PaaS Clouds
Buyer's Guide
Download our free Google App Engine Report and get advice and tips from experienced pros sharing their opinions.