When comparing Microsoft Azure vs Heroku, the Slant community recommends Heroku for most people. In the question“What are the best cloud platforms as a service providers?” Heroku is ranked 2nd while Microsoft Azure is ranked 7th. The most important reason people chose Heroku is:
Getting started with Heroku is very easy. It's a very straightforward procedure and a beginner can set up their first app in two minutes. Often it's just a matter of a couple of `git` commands and it's all set up and running. The official Heroku [docmentation](https://devcenter.heroku.com/) also helps a lot.
Ranked in these QuestionsQuestion Ranking
Pro Supports running Windows Server
Most, if not all, of the major cloud PaaS providers offer a Linux variant to host your applications. Windows Azure, being a Microsoft product obviously, supports Windows in addition to Linux.
Pro Linux Instances
The Azure platform has been supporting Linux VMs for a while now and has Linux distributions readily available in the catalogue.
Pro Free Tier
Microsoft Azure offers a Free Tier option that allows you to spawn a BST-1 instance that has 750 free hours.
Pro Easy to start with
Getting started with Heroku is very easy. It's a very straightforward procedure and a beginner can set up their first app in two minutes. Often it's just a matter of a couple of
git commands and it's all set up and running. The official Heroku docmentation also helps a lot.
Pro Excellent error logs
When your deploy fails you see a legitimate error log. Many of the other PaaS give you nondescript messages and debugging is a pain. Debugging Heroku wins by comparison.
Pro Add-ons let you easily add features and technologies
Heroku has a vast list of plugins and services that can be added to an instance. These plugins cover things from databases to email systems. This remove the task of having to install services and setting them up manually. Heroku does it all for you.
Pro Simple scaling
Heroku instances can easily be scaled up or down by increasing or decreasing the number of available dynos for that instance. This can be done through the CLI or through Heroku's web UI.
Pro Dedicated build servers
Heroku has dedicated servers for building app dependencies, to ensure that you won't have issues like "out of memory" errors when deploying your app.
Heroku is one of the oldest PaaS providers. The fact that it's been around for such a long time means that it had a lot of time to mature over the years. There's also a massive number of articles, guides and tutorials on Heroku out there for beginners and advanced users.
Pro Free option
Heroku offers a free tier which contains a single dyno instance. It offers 512MB of memory and 100MB swap space.
Even though in the context of Pay-as-you-go services, it's cost effective, but monthly pricing for these services are quite higher than competitors.
Con Constrained by addons
If you want to fully customize your production environment, then Heroku can be seriously constraining. Installing libraries or services can not be done unless there is already a Heroku plugin for it.
Con Further deployments are slow
While starting with Heroku is fast and easy, and the first few deployments are actually very fast, larger applications tend to have slower deployments. It takes some time for the dynos to restart and while they are restarting the application is completely offline. Which means that you can lose precious seconds of application time.
Con Really expensive
Heroku starts getting really expensive once you leave that free tier. It's not just the bare Heroku service that is costly, the addons as well are very pricey.