AppFog was a cloud-agnostic application and infrastructure management platform used to manage workloads across on-premises and third-party cloud environments. It has been discontinued.
$0
Google App Engine
Score 8.2 out of 10
N/A
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
gcloud CLI
Score 8.8 out of 10
N/A
The Google Cloud CLI is a set of tools to create and manage Google Cloud resources. Its tools can be used to perform many common platform tasks from the command line or through scripts and other automation.
N/A
Pricing
AppFog (discontinued)
Google App Engine
Google Cloud CLI
Editions & Modules
No answers on this topic
Starting Price
$0.05
Per Hour Per Instance
Max Price
$0.30
Per Hour Per Instance
No answers on this topic
Offerings
Pricing Offerings
AppFog (discontinued)
Google App Engine
gcloud CLI
Free Trial
No
No
No
Free/Freemium Version
Yes
Yes
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
AppFog (discontinued)
Google App Engine
Google Cloud CLI
Considered Multiple Products
AppFog (discontinued)
Verified User
Team Lead
Chose AppFog (discontinued)
Appfog was one of the requirements of our project since it was the fastest growing PAAS provider. Also it was easy to deploy an application with multiple options to choose for the development environment for our application. It was "ALL in ONE."
It was very good to use in small scale projects. Considering the high end projects with many instances and multi-platform architectures, it is better to test before the application is deployed. I think few of the questions can be general - who are the system users and what size is the application focussing on? How much resources are required? Will the application require any additional services?
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.
it is great for automating tasks like deploying VMs, running BigQuery and managing cloud resources at scale. It is much faster than the UI for repetitive actions and allows you to easily script and scale progress. However it is not ideal for beginners
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)
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.
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
Google Cloud CLI is highly usable once you’re past the basics, especially for engineers and DevOps teams who live in the terminal. It’s powerful, consistent, and scriptable, which makes it excellent for repeatable workflows, automation, and day-to-day cloud operations. The command structure is generally logical, tab-completion and help flags are solid, and it integrates cleanly into CI/CD pipelines—huge wins for productivity
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.
Primarily because it used to have a good free tier earlier, which it does not anymore. It's simple, and things are available to use. Compared to it's competitors, it does has less features, but that kind of acts in its favor. That adds to the simplicity, and ease of use for a new user.
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.
Google Cloud CLI stacks up well against other cloud and infrastructure CLIs by balancing power, consistency, and automation readiness, especially in production environments. Compared to AWS CLI, it’s more opinionated and readable, with better defaults and a more coherent command structure across services. Compared to Azure CLI, it’s less beginner-friendly but offers deeper control and is better suited for complex, large-scale workflows.
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.