AppHarbor vs Google App Engine: What are the differences?
Developers describe AppHarbor as "Instantly deploy and scale .NET applications". AppHarbor is a fully hosted .NET Platform as a Service. AppHarbor can deploy and scale any standard .NET application to the cloud. On the other hand, Google App Engine is detailed as "Build web applications on the same scalable systems that power Google applications". Google has a reputation for highly reliable, high performance infrastructure. With App Engine you can take advantage of the 10 years of knowledge Google has in running massively scalable, performance driven systems. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow.
AppHarbor and Google App Engine belong to "Platform as a Service" category of the tech stack.
Some of the features offered by AppHarbor are:
- You push .NET and Windows code to AppHarbor using Git, Mercurial, Subversion or Team Foundation Server with the complimentary Git service or through integrations offered in collaboration with Bitbucket, CodePlex and GitHub.
- When AppHarbor receives your code it will be built by a build server. If the code compiles all unit tests contained in the compiled assemblies will be run. The result and progress of the build and unit test status can be monitored on the application dashboard. AppHarbor will call any service hooks that you add to notify you of the build result.
- If everything checks out the application is deployed and configured on AppHarbor application servers. AppHarbor can scale an application vertically and horizontally within seconds for better request throughout, performance and failover. AppHarbor balance load across all instances running that application. Scaling an application gives higher request thoughput, redundancy in case of instance failure and better performance.
On the other hand, Google App Engine provides the following key features:
- Zero to sixty: Scale your app automatically without worrying about managing machines.
- Supercharged APIs: Supercharge your app with services such as Task Queue, XMPP, and Cloud SQL, all powered by the same infrastructure that powers the Google services you use every day.
- You're in control: Manage your application with a simple, web-based dashboard allowing you to customize your app's performance.
"Has a totally free account option" is the top reason why over 7 developers like AppHarbor, while over 140 developers mention "Easy to deploy" as the leading cause for choosing Google App Engine.
What is AppHarbor?
What is Google App Engine?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using AppHarbor?
What are the cons of using Google App Engine?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
AppHarbor is an amazing tool for indie developers or startups that are just getting on their feet. To put it short, AppHarbor is the Heroku of .NET, being developer friendly, cost effective and performant.
Their platform has some nice features including the plugins (integrations with different services such as shared or dedicated RDBMS instances, document repositories, messaging queues, logging and monitoring services, etc.) that are extremely easy to use, and especially integrations with BitBucket and GitHub.
It's such a pleasure to work with the integrations mentioned, that whenever a developer pushes commits to the selected branch, AppHarbor automatically pulls, updates, builds, runs the unit tests and deploys. The cream of the crop is the fact that even the free tier supports this workflow which is practically a continuous delivery approach. And this makes AppHarbor perfect for startups and independent developers.
And, for established companies, I have to add the fact that their customer support is quite good.
With Cloud Endpoints you can create and deploy mobile backend in one hour or less. And it is free (until you need extra scale). I would not recommend to use Java - python is faster and has all new appengine features.
Pros: everything is in one place: task queue, cron, backend instances for data processing, datastore, mapreduce. Cons: you cannot easily move your code from GAE. Even with special 3rd party services.
With Cloud Endpoints you can create and deploy mobile backend in one hour or less.
PaaS for back-end components, including external data ingestion APIs, front-end web service APIs, hosting of static front-end application assets, back-end data processing pipeline microservices, APIs to storage infrastructure (Cloud SQL and Memcached), and data processing pipeline task queues and cron jobs. Task queue fan-out and auto-scaling of back-end microservice instances provide parallelism for high velocity data processing.
checking a swap require a lot of cpu resource, roster normally come out same day of month, every month, at a particular time. Which make very high spike, our flag ship product, iSwap, with the capability looking swap possibility with 10000 other rosters base on user critieria, you need a cloud computing give you this magnitude of computing power. gae did it nicely, user friendly, easy to you, low cost.
App engine fills in the gaps in the increasingly smaller case where it's necessary for us to run our own APIs.
Very easy to make cloud computing of ML models , and use containers like Kubernetes.