20533 Who maintains and patches your servers in a PaaS web solution

20533 Who maintains and patches your servers in a PaaS web solution

This is a primary concern for any Enterprise web solution project.

For others the question may arise when you consider moving part of your own service to  PaaS layer

See the sample scenarios in Module 13 of MOC 20533 - PaaS is sold as a platform where the architects do not need to worry about patching and maintaining the servers

Most of the promotional material and insider blogs cover just that - general comparisons.  The very last article is quite specific about patching and upgrades of web components like ASP.NET - You want to pay particular attention to server restarts and also consider deployment options like scripting, Chef, Puppet or Jenkins - mentioned in a previous article


New Services in Azure
https://azure.microsoft.com/en-us/services/

PaaS overview - Azure specific
http://robertgreiner.com/2014/03/windows-azure-iaas-paas-saas-overview/

Dated but specific to Government clients
https://www.microsoft.com/industry/government/guides/cloud_computing/5-PaaS.aspx

Other PaaS providers
http://www.tomsitpro.com/articles/paas-software-development-cloud-computing-multi-tenancy,2-591.html

2013 article but mentions updating at startup
https://smist08.wordpress.com/2013/01/13/azure-and-paas-versus-iaas/