Blog

Azure App Service Update – What Does It Mean For You?

  |   Microsoft Azure, Our Blog   |   No comment

Microsoft continues to make big moves toward becoming the platform for new breeds of apps, by building on existing services.  If you haven’t already heard, Microsoft unveiled Azure App Service at the end of March, which was built upon already existing services, including Azure Websites, Mobile Services and Biztalk Services, and will begin a migration for users of Azure Websites to the new service (same price).  The goal is to provide one platform to build cloud based apps for any device. Earlier versions of Azure services for web sites and mobile apps required two different platforms, tools and technologies.  With Azure App Service, Microsoft wants developers to seamlessly create apps for any device.

What does this mean for developers?

  • One integrated App Service offering; allowing developers to run both Web and Mobile Apps using a single Azure App Service deployment without managing and paying for a separate web and mobile backend.
  • Single service for building web, logic, API and mobile apps (on any platform, any device)
  • Tools for automating business processes across cloud services
  • New service for building and consuming APIs
  • Staging and production slots
  • Better B2B and B2C engagement

What does it mean if you are already using Azure Web Sites?  No impact. The new Azure App Service retains 100% of functionality of Azure Web sites.

What does it mean if you are using Mobile Services? No impact for existing apps. However, it comes with all other features of Azure Websites like load balancing, Traffic Manager etc. But if you want to utilize the benefits of Azure App Service, we would suggest that you should convert and deploy them as App Service Mobile App.

Other capabilities which remain:

  • Support for .NET, Node.js, Java, PHP, and Python code
  • Built-in AutoScale support (automatically scale up/down based on real-world load; quickly set up scale-able websites and back-end tools)
  • Integrated Visual Studio publishing as well as FTP publishing
  • Continuous Integration/Deployment support with Visual Studio Online, GitHub, and BitBucket
  • Virtual networking support and hybrid connections to on-premises networks and databases
  • Staged deployment and test in production support
  • WebJob support for long running background tasks
No Comments

Sorry, the comment form is closed at this time.