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
IBM Cloudability
Score 8.8 out of 10
N/A
IBM Cloudability is a cloud cost management and optimization (FinOps) tool that enables IT, finance, and business teams to optimize their cloud spend across all cost sources, all maturity levels, and for all stakeholders.
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.
I don't have much exposure to the tool. I mean, I'm relatively new to using it as a platform, but I haven't really seen the benefit, especially with the actual renewal talks at the company. I'm not seeing what AWS native solutions are, how probability improves on that as opposed to just using AWS and just, I don't know. I'm not seeing the benefit, at least in my eyes.
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)
For me, it is a lot of anomaly detection and I think there's a lot of improvement that can be made to show anomalies that happen over time because if it's just day to day or week to week, you may not see the change. But if you see the trend over a period of time, show me something that has grown 40%, 50% over the past three months and maybe you can do those things and we just haven't figured them out yet. So we are very new to the product, but I think anomaly detection for me is one of the bigger things.
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.
Cloudability has been one solution for almost all of our FinOps needs. Except for Data transfer costs, we have covered all use cases and have made significant savings across our cloud infrastructure. Reporting has provided management a deeper analysis into their spending and helped them forecast their budgets for next year
I had to revisit the UI after a year of just setting up and forgetting. The UI got some improvements but the amount of navigation we have to go through to setup a new app has increased but also got easier to setup. Gemini now is integrated and make getting answers faster
I gave the IBM Cloudability a 7/10 because it is good, but it could improve in some places. It is easy to get data uploaded and ready to view, but it is only up to a certain point in time, and not live data. As for how it looks, the interface is good for viewing, however navigation could be a little better, maybe supported with a roadmap.
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.
While there have been few support cases where the experience was good. But in multiple support cases it's firstly delayed and even after weeks or months of time, team is not able to provide us with the RCA of the issue. All they are claiming is the issue is now fixed which I still see coming back after few days or weeks as we've never identified and addressed the root cause.
Training was adequate, but the real learning begins when you start using the product, like most things. All major functions were covered so as an entry point, was a good introduction to the product. The training pace was good as well, the areas were covered in decent depth, without being too much of an information overload.
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.
Before Apptio we extensively used the cloud native and in house automated and developed cost optimization tool using python , powershell and leveraging the various cloud native services like AWS systems manager , Azure Functions and Azure automation run books.
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.
