Azure Cloud Services vs. Heroku Platform

I like the security provided by Microsoft Cloud Platform that gives us comfort that our Clouds data and applications are safe and secure with excellent backups and recovery capabilities and our entire organization depend on this platform for effective data migration. The system integrations with this platform are highly intuitive with the ease to customize its API and excellent performance monitoring capability to all our Clouds applications.

Heroku is very well-suited to early stage and/or rapidly changing projects. It is great for getting moving quickly or changing direction quickly. In scenarios where there is already scale or well-defined requirements, it may be preferable to set things up directly on AWS or another cloud provider to avoid the additional costs of Heroku as the middleman.

Incentivized

• Azure excels in providing scalable infrastructure and services. For example, organizations can use Azure Virtual Machines to dynamically adjust computing resources based on demand.
• Azure's Platform as a Service (PaaS) offerings, such as Azure App Service, empower developers to focus on building applications without dealing with the underlying infrastructure.
• Azure seamlessly integrates with on-premises environments, facilitating a hybrid cloud approach.
• Azure Functions allows organizations to execute code in a serverless environment, triggering functions in response to events without the need to provision or manage servers.

• Amazingly clear and straightforward documentation (versus the quagmire of AWS docs).
• Deploy your entire site in one command.
• Setting up asynchronous job processing for long running operations (e.g. sending emails, making external API calls).
• A wonderful portfolio of tightly-integrated add-ons in their marketplace.

Incentivized

• Azure MySQL single server to flexible server migration
• Database Migration Services
• Azure VMs

Incentivized

• Could be less expensive, although you get what you pay for
• Sleeping apps can be an annoyance: Heroku automatically puts your apps in sleep mode and they have to spin back up after periods of inactivity. Much of this can be solved but it requires working around the built-in functionality. I understand why they do it but it's an area that could be improved.
• Restrictions to server access means you can't customize as much as you could if you owned the server. But again, this is also a benefit because it's about convention over configuration. So you can't configure as much, but then, you typically don't have to.

Incentivized

Heroku is a critical and core part of our infrastructure that is serving our customers well. We are very satisfied with the cost of our solution. While it would be difficult to move away from Heroku, we have no plans to do so. We have had no major issues with it and it is a pleasure to use. Other products on the market might offer comparable functionality, but until we expose a need that Heroku cannot satisfy, we'll stay the course.

Incentivized

If you have basic backend and Git knowledge, deploying to Heroku is a breeze. It now supports many types of backends, including hybrid backends (ex: nginx + application server) through its build pack system. The dashboard is easy to use, and the CLI tools are well designed. Accessing the add-ons is also easy. It uses an SSO-type system so you don't have to re-sign in to view the add-on dashboards.

Incentivized

Heroku availability correlates pretty strongly to AWS US EAST availability. We had a couple of times where there was a Heroku-specific issue but not for the last 7-8 months.

The only issue that I ever have is that about 1 out of 20 deployments (git push) will hang and need to be cancelled and done again.

I've used it for many years without facing any major problem. It's not hard at all to get used to it, it's documentation is outstanding and simple. We are close to 2020 and I don't think most of the existing companies or startups should still face old problems such as wasting time deploying code and calculate computing resources.

Incentivized

Be ready to pay a bit more than expected in the beginning if you're migrating from a big server. The application is probably not ready for the change and you have to keep improving it with time.

It's also important to consider that you can't save anything to the disc as it will be lost when your application restarts, so you have to think about using something like S3.

Incentivized

I feel AWS offers a robust and versatile platform for cloud infrastructure and services. It's scalability, reliability array of tools make it a top choice for businesses of all sizes. AWS has better open source communities such as Linux, Jenkins and GitHub in comparison to Azure service cloud

Heroku has advantages over Docker, Google App Engine and AWS products, but it depends largely on your use case. If you are already in AWS, it's probably in your best interest to stay with AWS products. However, other "Cloud Formation/Orchestration" products like Docker are typically lacking the ease-of-use factor that allows you to get up and running with Heroku quickly.

Incentivized

• Remote data accessibility via the platform is effective.
• Data security through the system is guaranteed.
• Easy data recovery solution.

Incentivized

• It has been critical in seamlessly operating our platform with runs all of our programs.
• It has been impressive with its ability to scale quickly which results in the growth of our work.
• It allows for tracking of different features which allows for quick problem solving which saves us time.