The type of platform my company generally uses for a project that needs no maintenance of any infrastructure for our customers and needs only Lambda functions is Google App Engine.
Principal Technical Architect at NTT Security
The tool offers reliability and ease of management
Pros and Cons
- "The product's initial setup phase was straightforward, considering that there is good documentation explaining the implementation part of it."
- "The support for the Indian region is not as good as compared to the support that is offered to the regions in Europe."
What is our primary use case?
What is most valuable?
The most valuable features of the solution are reliability and the depth of Google App Engine's services, which are some of the reasons why I would like to give it a high rating when compared to AWS.
What needs improvement?
The support for the Indian region is not as good as compared to the support that is offered to the regions in Europe. My company faces a lot of problems with the support team, especially when Google's technical team is not able to help us immediately when we are stuck with something related to the tool. The support of the product is an area where improvements are required.
Google App Engine is a good product, and its support needs to be improved as it is a new technology that few people know about. There is a need to spread some awareness about the product while also ensuring that some online forums related to the product need to be updated with a lot of documentation related to the tool.
For how long have I used the solution?
I have been using Google App Engine for six years. My company has a partnership with Google.
Buyer's Guide
Google App Engine
June 2025

Learn what your peers think about Google App Engine. Get advice and tips from experienced pros sharing their opinions. Updated: June 2025.
860,632 professionals have used our research since 2012.
What do I think about the stability of the solution?
I have not had any issues with the stability of the product.
What do I think about the scalability of the solution?
The scalability of the product is fine.
Around 1,500 customers of my company use the product.
How are customer service and support?
I rate the solution's technical support in India a five out of ten.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
In comparison to other solutions offering similar functionalities, I can say that I have not found any issues with Google App Engine. Google App Engine is at par with the best solutions in the market.
How was the initial setup?
The product's initial setup phase was straightforward, considering that there is good documentation explaining the implementation part of it.
Initially, our company invested time in understanding the entire product. My company went ahead with the PoC phase based on the briefing we received from Google's team, after which we went ahead with the production part.
The solution can be deployed in fifteen days, though Google had claimed that the process might take a month.
A lot of people, including developers and Google administrators, were involved in the product's development process.
What other advice do I have?
The use case where the product has significantly improved the development was attached to one of the scenarios where one of our company's customers wanted a tool to deal with continuous integration and deployments in the infrastructure. In the aforementioned scenario, my company used Google App Engine to deploy an infrastructure for our customer, and the product helped solve a lot of problems, reducing the time required to complete the project by half.
Google App Engine has supported the need for scalable applications for our company's customers since whenever the tool was used, it used to get integrated with a lot of new technologies, like Chef, Puppet, and with some of the APIs, after which my company was able to deploy the product on an on-premises model for our customer.
The feature of Google App Engine that I found to be the most essential for workflows is the high availability and scalability.
The serverless aspect of Google App Engine has benefited our company's customers since it has reduced the time required for the implementation of their applications. The tool also has been able to solve conflicts between developers and the people in operations. The tool offers the convenience of time and ease of implementation, which has improved and solved a lot of problems. The bug-fixing process in the tool is very fast compared to the manual thing.
The product does not require any maintenance.
The advantages of the product revolve around the fact that it offers a lot of depth, ease of management, scalability, and is fast. Developing and hosting applications is possible with Google App Engine. Google App Engine is more beneficial for those who deal in e-commerce.
I guess Google App Engine is a very good tool for infrastructures or when you need some machines that work twenty-four hours, seven days a week. Google App Engine is like a FaaS tool for its users, so users don't need to maintain any infrastructure, thereby drastically reducing their costs. Google App Engine is a very user-friendly, accessible, highly scalable product that allows users to opt for a pay-as-you-go model.
I rate the overall tool an eight out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Programma en project manager at a consultancy with 51-200 employees
Powerful, simple to use, and good documentation
Pros and Cons
- "It is simple to use. It is much simpler than AWS. It is also very powerful."
- "I would like a simpler deployment tool on laptops. It is a bit complicated at the moment. We know how to do it, but it could be easier to deploy it on laptops."
What is our primary use case?
We have an industrial maintenance program application, and we log maintenance data.
We are using its latest version. When there is a new upgrade, we just upgrade. In terms of deployment, the development suite is on laptops, but the service is on the cloud.
What is most valuable?
It is simple to use. It is much simpler than AWS. It is also very powerful.
What needs improvement?
I would like a simpler deployment tool on laptops. It is a bit complicated at the moment. We know how to do it, but it could be easier to deploy it on laptops.
For how long have I used the solution?
I have been using it for two and a half years.
What do I think about the stability of the solution?
It is stable. There are no issues.
What do I think about the scalability of the solution?
It is scalable.
How are customer service and support?
We haven't used their support, but the documentation is very good. We also use their Stack Overflow service, which is quite okay.
How was the initial setup?
Its initial setup is very complex.
What other advice do I have?
I'm quite happy with it. I would rate it an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Google
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Google App Engine
June 2025

Learn what your peers think about Google App Engine. Get advice and tips from experienced pros sharing their opinions. Updated: June 2025.
860,632 professionals have used our research since 2012.
Teaching Assistant at a government with 201-500 employees
Ability to test before deployment and security authorization are key features
Pros and Cons
- "Seurity features - unauthorized individuals are unable to access certain applications."
- "Difficult to assess how pricing is managed."
What is our primary use case?
This solution is a model for us right now, and I'm using it with my classmates. We are resellers. I'm currently a Masters student and teaching assistant.
What is most valuable?
The most valuable feature in the solution is basically the security where you're required to use the AIP to initialize the accessibility process. It means that unauthorized individuals are unable to access certain applications. Mostly it is based on the workplace environment. Testing deployments is also a valuable feature as it enables you to test your app before you deploy on cloud.
What needs improvement?
Everything so far has gone smoothly, I've never had a struggle with the solution.
In terms of product improvement, when it comes to billing, I think they should include something that would give the client or user an indication of what's happening so they can be aware of how pricing is being managed.
For how long have I used the solution?
I've been using this solution for the past few months.
What do I think about the stability of the solution?
It's a stable solution.
What do I think about the scalability of the solution?
I think it's a scalable solution. because basically you can add the amount of storage you want. When it comes to bugs, mostly there are no errors. It has happened, but rarely although I do think a little bit of improvement could be made in that area.
How was the initial setup?
Initial installation is very straightforward, it takes no more than 45 minutes.
What other advice do I have?
This solution is cheaper and more efficient compared to other similar solutions with cloud vendors.
I would rate this solution an eight out of 10.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
CEO/Programmer at Tech Elight
An easy to deploy solution that's scalable and not too expensive
Pros and Cons
- "The initial setup is okay. It's not too complex. Deployment took about one day."
- "There needs to be more directions in terms of how to use the solution."
What is our primary use case?
We primarily use the solution for business purposes for our clients. We develop software.
What is most valuable?
The solution allows you to create apps right on Google.
What needs improvement?
It would be helpful if they could improve the user interface. It could use some modifications.
There needs to be more directions in terms of how to use the solution.
For how long have I used the solution?
I've been using the solution for five or more years.
What do I think about the stability of the solution?
The solution is mostly stable.
What do I think about the scalability of the solution?
The solution is scalable.
How was the initial setup?
The initial setup is okay. It's not too complex. Deployment took about one day.
What about the implementation team?
We handled the deployment ourselves. There were four of us, including a back-end developer, a front-end developer, and an HR manager.
What's my experience with pricing, setup cost, and licensing?
The pricing is okay. It's not too expensive.
What other advice do I have?
I'd rate the solution ten out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
IT Manager Assistant at Aras
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: My company does not have a business relationship with this vendor other than being a customer.
Personal docente at U.E.N Aime Bonpland
Its ability to integrate with most devices helps users who have different or old devices
Pros and Cons
- "Its ability to integrate with most devices helps users who have different or old devices."
- "Data consumption of the device could be improved."
What is our primary use case?
This solution is very efficient and easy to use. It is easily integrated with the needs of each user without the having to go to a third party.
How has it helped my organization?
Each application we choose meets the needs of the organization. The applications are very interactive and their prices are very accessible to each user.
What is most valuable?
Its ability to integrate with most devices helps users who have different or old devices.
What needs improvement?
Data consumption of the device could be improved.
For how long have I used the solution?
One to three years.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
System Programmer at a non-profit with 201-500 employees
Allows you to test your development. The programming interface is not easy.
What is most valuable?
Free Tier is basic if you simply want to test your development or if are not sure whether the product you are trying to launch will be successful. Free tier is unlimited in time. Other platforms used to offer a one year Free Tier. This unlimited time feature lets you work without worrying about money. If you need to pay, you know you are getting traffic.
Being that Free Tier is getting better on other platforms. I think Google App Engine Free Tier will keep on beating its rivals.
How has it helped my organization?
It lets you forget about everything not related to development, while allowing great load variations.
What needs improvement?
The programming interface is not easy, but I can't talk deeply about it, as I have used a framework which hid the API.
I can't detail anything about GAE API, as I didn't use it. Nevertheless, I could have a look at it. I could especially look at what is related to its DataStore database, in terms of its keys or its ancestors.
It seems to be a totally different approach, compared to traditional SQL databases. The Web2py framework hides this complexity.
I searched for some information about how to use GAE API, both on official
docs, forums or books. The conclusion I took after these searches was this
API was not easy to use. And this reality was one of the reason why I
started searching for a framework that could hide GAE API. I have to
recognize this impression could be caused because of my previous work with
SQL related API -note that GAE is build upon a NoSQL database.
For how long have I used the solution?
I have used Google App Engine for three months.
What do I think about the stability of the solution?
I have not had any stability issues.
What do I think about the scalability of the solution?
I have not had any scalability issues.
How are customer service and technical support?
I did not need to use support.
Which solution did I use previously and why did I switch?
I didn’t have a previous solution. This was my first option, due to it being the only one with a real free tier.
How was the initial setup?
The setup was really straightforward thanks to the framework. It does not seem to be difficult.
What's my experience with pricing, setup cost, and licensing?
It has really competitive pricing when talking about low usage tiers, but prices rise quicker than other options.
Which other solutions did I evaluate?
I checked documentation about other solutions:
- PaaS (Heroku)
- IaaS (Amazon, Azure, and Google Cloud)
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Developer at a media company with 51-200 employees
Good-bye App Engine
I’d been running my web site for comedians LaffQ.com in Google App Engine for nearly two years. Google App Engine seemed pretty neat when it first came out: it was the only free hosting service I knew of where you could deploy dynamic Python apps (using Django no less, a framework I was already familiar with) with the promise of Google managing the backups, scaling, and provisioning.
But as time went on, the sunny optimism began to fade. Although Google supported Django, it uses a proprietary BigTable-backed database which was not compatible with Django’s object-relational wrapper (ORM). The originally unbelievably high free limits during the beta period which reduced drastically, in some cases absurdly, when the product came out of beta. Visiting my internal operations page just twice could blow out nearly the entire day’s quota because it produced counts of many tables — so each item counted towards a daily quota of 50000 “small operations”.
Developing for Google App Engine was always a pain. It was non-standard enough that a lot of libraries and tools wouldn’t work or need annoying changes. There was a single point of documentation, written in a sort of corporate Google-ese — not horrible, but not the nicest documentation I ever read. There were a lot of layers of abstraction. It was proprietary. It was slow to fetch data. The pdb debugger didn’t work very well. Getting data out of production was an ordeal. It was even hard to launch a instance on the command line, which meant on those rare occasions when I decided to do development on my Linux netbook, I spent most of my time getting the newest version of Google App Engine to work again.
I don’t exactly remember how or why, but late one Sunday evening in November I suddenly came up with the bright idea to port the Google App Engine infrastructure to “sqlite” (as I referred to it in my head), ie. to use the standard Django database back-end with the idea to deploy it to some unknown host using sqlite3. I started almost immediately, figuring at the very worst, it would just be an abandoned experiment.
It turned out to be… well, if not “surprisingly easy”, remarkably painless. By Monday afternoon, I had gotten most of the core public functionality working just fine (insert show, edit show, delete show, list shows). The data model ported straight across with, one exception being a GeoPt latitude/longitude structure, which I simply reformatted into a string containing a comma-separated pair (which is was probably stored as in Google anyway).
By 9 pm on Monday, my entire test suite was passing. The internal pages hadn’t been ported yet, nor the “post on Facebook” functionality.
I decided to work on the non-critical internal pages first, or else I wouldn’t have any excuse to not deploy (and that’s scary!). I ported these components which gave the code base a chance to “set” (like Jello™) and time for that unease associated with massive changes to dissipate somewhat.
Some changes that occurred more than once:
- adding “objects” everywhere, so Model.get becomes Model.objects.get
- changing Property to Field (ndb.StringProperty => models.CharField for example)
- ndb.KeyProperty => models.ForeignKey
- put => save
- key.get. => key.
- .query() => .objects
- required=False => null=True
- obj.key.delete() => obj.delete()
- query.order => query.order_by
- query.filter works very differently (no more fancy Google App Engine custom types based on operator overloading and deferred evaluation… fancy, but pretty opaque)
On Tuesday, I started working on the automated posts to Facebook. Not much needed to change here, but it was a bit nasty as there were only limited automated tests for this, so I had to be very cautious. Somewhere along the line, I decided I would deploy on my unlimited Dreamhost account (promo code: “RICHARD_SHARES”), which costs about $9/month and already hosts a bunch of domains. There were a few gotchas in getting the wsgi configuration working with Django (and it was tremendously difficult to debug until I hit on this idea of marshaling the requests to a file, then invoking the server by hand using the marshaled request), but this was reasonably straightforward, and I had built a local installation of Python 2.7 in the past, so I reused that.
I worked on the code to import the data. Google Data Export is another things that’s way too complex and slow, but I had done a trial run of the export on Sunday, so I used that as a testbed. I found some sample code to read the sqlite database (which is very simple) into Google Entity objects, so it was fairly simple to read properties out of the Google objects and put them into Django objects. I ended up doing it in two passes; the first pass included root objects that other objects have foreign keys to, which ensures that the second pass can refer to those already created objects without dangling foreign keys.
I waited until midnight, so the daily stats would be generated on Google, with Google data, then immediately put the site into read-only mode on Google and began the dump of data from Google. It was infuriatingly slow. It finally finished around 12:42 am, so about 40 minutes total, to produce a 21 MB sqlite database file. Finally, one little file with ALL my LaffQ data in it!
Here’s the script that converted the exported Google App Engine data to native Django objects in sqlite3: https://gist.github.com/richardkiss/4576523
I had already brought up the new site on Dreamhost, using two day old data, so it was just a matter of running the conversion tool, which read the Google sqlite database (which was essentially a BigTable dump, with one entity) and wrote out the Django sqlite database (which much more closely resembled the actual structure of data in my database). The new sqlite file was 8.7 MB. Compressed with bzip2, it was under 2 MB. That was the entirety of my web site data that took Google 40 minutes to export!!!
I copied it to Dreamhost in about five seconds, deployed it, restarted the Django app, and poked around a bit. Everything seemed to be in order and up to date, so I update DNS to point to the Dreamhost version of the web site, and waited for the change to propagate around the world (it’s funny to think about how LaffQ came up at different times for different people).
One thing I forgot is the Facebook integration required SSL. I didn’t have an SSL certificate (or a unique IP!) so I was flustered for a bit. I thought about how this used to work: it went to the laffq.appspot.com domain, the Google domain that supports SSL for free (signed with a Google appspot.com SSL certificate). Then I realized, I could just write a tiny Google App Engine app that proxied requests to https://laffq.appspot.com/ by fetching content from laffq.com. These pages are very low traffic (since they don’t really do anything), and it worked! (I had problems serving CSS to Chrome, which were resolved by making sure the content-type header was set correctly).
I’m kind of glad I didn’t remember this until it was deployed because I didn’t see the answer right away, and it might have made me not go through with it due to my tendency to know every move in advance.
All in all, the port went unbelievably well. The sqlite version is MUCH faster than Google even though memcache is no longer in the mix (I do use built-in Django caching in the same memory space as the Django app, although I’m pretty sure I could turn it off and it would still be very fast). It uses very little CPU on Dreamhost, and there are no annoyingly arbitrary quotas.
Since then, my work on LaffQ has accelerated beyond my wildest dreams. I didn’t realize just how much the Google App Engine restrictions were holding me back. Now I can back up my entire production database in just a few seconds. I can run a copy of production database locally, which gives me a much better feel for how changes will perform with production data, so I use production data in development all the time. This gives me a much better feeling about new features. Debugging is much easier. Deploying is as simple as a git push/git pull. I can look at logs. I can make tweaks in production. I can ssh to the production machine. I can diagnose problems in production. Pretty much everything about it is better. I’ve refactored, tweaked, optimized, added tests. It’s code I’m almost proud of now. (Almost.)
I saw on Hacker News the other day about how Google App Engine was down. I was happy it didn’t affect me.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.

Buyer's Guide
Download our free Google App Engine Report and get advice and tips from experienced pros
sharing their opinions.
Updated: June 2025
Product Categories
PaaS CloudsPopular Comparisons
Microsoft Azure
Amazon AWS
Red Hat OpenShift
Oracle Cloud Infrastructure (OCI)
VMware Tanzu Platform
Salesforce Platform
Pivotal Cloud Foundry
IBM Public Cloud
Amazon Lightsail
IBM Cloud Private
Buyer's Guide
Download our free Google App Engine Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Looking for a cost comparison evaluation for PaaS platforms
- When evaluating a Platform as a Service (PaaS), what aspects do you think are the most important to look out for?
- Pros/cons of Rackspace vs. other leading vendors?
- Cloud Computing: What are the top 3 benefits of public cloud computing in the enterprise?
- What are the main pros and cons of the various PaaS solutions on the market?
- What is the difference between IaaS, SaaS, and PaaS?
- Which platform do you prefer: Azure or AWS?
- If you anticipate needing to scale your application significantly, what is the best solution?
- PaaS solutions: Areas for improvement?
- Which cloud IaaS/PaaS platform would you recommend learning to a newbie?
My appreciation to IT central station for this wonderful opportunity.