2. Agenda What Kentico CMS needs to run on Azure Windows Azure doesn‘t have durable NTFS file system No write access to the application directory Application must be stateless SQL Azure – little bit different database Windows authentication Differences in development Azure SDKs
3. What Kentico CMS needs to run on Azure Kentico CMS 5.5 R2: Windows Azure compute services (ASP.NET web role) Optionally Windows Azure storage (blob storage) SQL Azure ASP NET Web role SQL Azure Azure storage
4.
5.
6.
7. Load balancer
8. Round robin algorithmInstance 2 Load balancer Challenges Synchronization of memory objects Storing of session state data Solution Web farms module (6.0) Use Azure session state provider Instance 3
9. Application must be stateless On-premise session state providers Azure session state providers
10. SQL Azure – little bit different database Few general differences: Main difference – SQL is relation database without additional features (Reporting services, integration services, ...). Reporting services are now in CTP Missing fulltext support Every table needs to have at least one clustered index From Kentico CMS point of view: No problem, question of changing connection string SQL migration wizard, http://sqlazuremw.codeplex.com/
11. Windows authentication Integrated Windows authentication doesn‘t work with ASP.NET web role WebDAV integration needs this type of authentication Possible solution – Windows Azure Connect
12. Differences in development Application which run under ASP.NET web role must be Web application project Kentico CMS 5.5 R2 – web site project New type of project, new configuration files
13. Azure SDKs Multiple versions Kentico CMS supports SDK 1.1 upper (latest is SDK 1.4) Breaking version – SDK 1.3, full IIS support, remote desktop, ... SDK 1.2 and lower – setting for internal role port is missing – minor issues with Kentico CMS SDK 1.3 and upper – Visual studio 2010 needed, issue with running Kentico CMS under full IIS in Visual studio – bug in SDK