I used Google App Engine about 10 months ago. We used it to deploy frontend services and backend services. We deployed through Google App Engine using both the standard environment and the flexible environment for different end services. Regarding integration capabilities, there were Google credentials features that made it easy to use other services from Google, such as Pub/Sub messaging service and other functionalities, which were very tightly integrated. I did not have to think about the authentication between the services as it was seamless, and I did not have to do any extra work to get the authentication part working. We were using approximately five or six services with Google App Engine, including three backend services and a couple of frontend services. Some of them used Google's Pub/Sub messaging service and Google's Maps APIs.
My usual use case for Google App Engine is related to SaaS applications where we create applications. For this purpose, we needed Google App Engine. We had concluded between AWS, Google GCP, and Microsoft Azure. At that particular time, we decided to use GCP because of the cost effectiveness and the support. We had a tie-up with Google for that particular application.
In my current company, my client is completely based on Google. They are using their domain from Google and mixing Google Cloud with AWS Cloud. When it comes to deploying our microservices or REST APIs over the cloud, I develop APIs and portals for the Service Request Development (SRD) team. There are a lot of SRD personnel involved, possibly around 1K users, with many leaders using the services globally due to my engagement with a major IT giant.
I am a Java developer and primarily use Google App Engine ( /products/google-app-engine-reviews ) for UI-based applications and hobby projects. I have used it for various applications, including CRM ( /categories/crm ) kind of applications. I test and create apps, primarily focusing on these use cases for my personal projects.
I deployed a Python Flask-based API on Google App Engine ( /products/google-app-engine-reviews ) using Firestore for real-time data storage. The platform's autoscaling capabilities allowed the apps to handle any increase in traffic without manual intervention. I also leveraged Cloud Pub/Sub for background processing tasks, ensuring smooth performance. Additionally, I used Stackdriver to monitor logs and identify optimization areas, making the deployment more efficient.
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.
Pre-Sales Solution Architect Manager at Qi Network
Reseller
Top 10
2023-07-18T12:45:07Z
Jul 18, 2023
We use the solution for migrating from on-premises to the cloud or for some collocations of software to Google Cloud. We work with App Engine and other serverless solutions like Cloud Run and Google Kubernetes Engine. Additionally, we have some clients working with App Engine.
Programma en project manager at a consultancy with 51-200 employees
Real User
2022-04-07T05:11:18Z
Apr 7, 2022
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.
Teaching Assistant at a government with 201-500 employees
Real User
2020-04-23T10:13:34Z
Apr 23, 2020
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.
Google App Engine is a Platform-as-a-Service (Paas) provider that equips web application developers with all the resources and tools that they need to develop, test, and run their applications on Google's infrastructure. Everything is built into the kit, so with one download of the SDK, you'll be well on your way to first-rate apps.
I used Google App Engine about 10 months ago. We used it to deploy frontend services and backend services. We deployed through Google App Engine using both the standard environment and the flexible environment for different end services. Regarding integration capabilities, there were Google credentials features that made it easy to use other services from Google, such as Pub/Sub messaging service and other functionalities, which were very tightly integrated. I did not have to think about the authentication between the services as it was seamless, and I did not have to do any extra work to get the authentication part working. We were using approximately five or six services with Google App Engine, including three backend services and a couple of frontend services. Some of them used Google's Pub/Sub messaging service and Google's Maps APIs.
My usual use case for Google App Engine is related to SaaS applications where we create applications. For this purpose, we needed Google App Engine. We had concluded between AWS, Google GCP, and Microsoft Azure. At that particular time, we decided to use GCP because of the cost effectiveness and the support. We had a tie-up with Google for that particular application.
In my current company, my client is completely based on Google. They are using their domain from Google and mixing Google Cloud with AWS Cloud. When it comes to deploying our microservices or REST APIs over the cloud, I develop APIs and portals for the Service Request Development (SRD) team. There are a lot of SRD personnel involved, possibly around 1K users, with many leaders using the services globally due to my engagement with a major IT giant.
I am a Java developer and primarily use Google App Engine ( /products/google-app-engine-reviews ) for UI-based applications and hobby projects. I have used it for various applications, including CRM ( /categories/crm ) kind of applications. I test and create apps, primarily focusing on these use cases for my personal projects.
I deployed a Python Flask-based API on Google App Engine ( /products/google-app-engine-reviews ) using Firestore for real-time data storage. The platform's autoscaling capabilities allowed the apps to handle any increase in traffic without manual intervention. I also leveraged Cloud Pub/Sub for background processing tasks, ensuring smooth performance. Additionally, I used Stackdriver to monitor logs and identify optimization areas, making the deployment more efficient.
I use the solution in my company to deploy web applications.
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.
We use the solution for migrating from on-premises to the cloud or for some collocations of software to Google Cloud. We work with App Engine and other serverless solutions like Cloud Run and Google Kubernetes Engine. Additionally, we have some clients working with App Engine.
A lot of services we offer are developed and hosted on App Engine,.
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.
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.
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.
We primarily use the solution for business purposes for our clients. We develop software.
We are using this application for learning purposes.
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.