AppFog (discontinued) vs. Azure App Service

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?

Incentivized

You may easily deploy your apps to Azure App Service if they were written in Visual Studio IDE (typically.NET applications). With a few clicks of the mouse, you may already deploy your application to a remote server using the Visual Studio IDE. As a result of the portal's bulk and complexity, I propose Heroku for less-experienced developers.

Incentivized

• Quick deployment of pre-built virtual machines
• Some of the virtual machines also are readily available with a pack of softwares
• Good Stability. Using it as a student, I have never experienced any downtime issues with the projects deployed on AppFog.

Incentivized

• Extremely easy to deploy and update from Visual Studio
• It integrates seamlessly with other Azure PaaS resources
• It has an in-depth integration with AppInsights, so you can understand errors and their root cause easily.
• Easy to create and delete, what is not the same case in a IaaS resource
• It escalates based on CPU workload and some other resource variables.
• Configuration changes are almost immediate
• Offers an excellent abstraction from hardware backend of the platform
• That's updated very often, saving time and the risk of a self-performed update over a IaaS
• That's really easy to develop for Web Apps
• It supports Function Apps and Web Apps into the same "cost black box"

Incentivized

• Though it is good and easy for developers, it lacks operational activities and monitoring tools.
• It is easy to deploy WAR on AppFog with its console but sometimes it can lack on the performance and feasibility.

Incentivized

• Jumps between resource sizes can get expensive
• You may wind up putting a lot of eggs in one basket--not necessarily a con but something to keep in mind (most of your data will likely be managed and processed through Microsoft products/services if you fully commit to Azure App Service).
• Learning new technology. If you're moving from on-premises to Azure App Service (or any cloud solutions), you'll likely have to rethink how things are done to achieve the same end results (and/or resources may become expensive quickly).

Incentivized

I have given this rating because Azure App Service performs very well in terms of speed, reliability, and reducing overhead, and improves overall team productivity, with a little scope for improvement in complex testing scenarios and configurations, scalability concerns in a large setup, and similar tracking and audit needs.

Incentivized

Microsoft has always been known for providing a high standard in terms of customer support and Azure App Service (and as a matter of fact the whole Azure Platform) is no exception. Azure App Service never caused us any issues and we only contacted their customer support for questions regarding server locations and pricing. I feel pretty satisfied with how they treat their customers.

Incentivized

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.

Incentivized

When we chose it, we did so because of its integration with Microsoft applications; now we need to integrate with AI, and Azure doesn't offer a good integration. That is the main reason to change it. It is still great to develop Windows- and Microsoft-based applications, but if we need to integrate with AI, Google wins by far.

Incentivized

• Our project was deployed with good efficiency and easily accessible.
• The platform was much recommeded across the groups and peers.

Incentivized

• Deployment of ASP.NET apps at the organization has been sped up.
• An option to offer access to the version control system on a third platform so that we could easily deploy our apps.
• Because of Azure App Service's scalability capabilities, the costs of running the services are kept to a minimum. As a result, we may save hundreds of dollars each month compared to the expenses of traditional servers by using fewer resources during slack periods.

Incentivized