Likelihood to Recommend 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.
Read full review RedHat OpenShift is not only suited for IBM Cloud but can run in ANY cloud. We installed in Azure Cloud, for example. It can also run on Linux servers or a Power 9 machine. It is built for multi-cloud or on-prem environments. IBM support provides such excellent guidance in the installation and configuration that no other product on the market can beat it.
Read full review Pros 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. Read full review Multiclick provisioning of resources makes it super easy to manage pods and deployments. We don't have to maintain code for the same In built security features and customizability ensures that organization wide standards are integrated well into the containers Automated backups, scale ups and fail recovery makes sure of minimal down time Read full review Cons 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) Read full review I wish it had better compatibility with docker file syntax. We had issues when it couldn't build standard docker files Wish it had better documentation Wish they offered fully supported client libraries for the Openshift API rather than dumping it on a 3rd party Read full review Likelihood to Renew 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.
Read full review Usability 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.
Read full review Support Rating 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.
Read full review I think response time for IBM Cloud support should be improved.
Read full review Alternatives Considered 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.
Read full review We evaluated a number of potential solutions and ultimately chose Red Hat OpenShift because it was compatible with our existing technology. Time and costs savings have been realized throughout the company since we implemented Red Hat OpenShift, and the IT department has been freed up to focus on activities that are more valuable.
Read full review Return on Investment Effective employee adoption through ease of use. 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. Read full review Our customer satisfaction and NPS score has had positive outcomes based on new architecture We are focused on business outcomes vs running the service and maintenance OpenShift on IBM Cloud has had a direct, positive impact on TCO, ROI, and payback period Our staff is more focused on higher-level business activities, i.e. acquiring & customer retention Read full review ScreenShots