Differences Between On Premise And Windows Azure
Download as PPTX, PDF0 likes2,041 views
The document discusses the differences between on-premise hosting and Windows Azure for Kentico CMS, highlighting issues such as the lack of a durable NTFS file system and the need for stateless applications. Key challenges include synchronization of instance data, web analytic modules, and the transition from web site projects to web application projects in the Azure environment. It also notes differences in SQL database features and development requirements with various Azure SDK versions.
Differences Between On Premise And Windows Azure
- 1. Differences between On-premise and Windows AzureDominik Pintér (dominikp@kentico.com), Kentico software
- 2. AgendaWhat Kentico CMS needs to run on AzureWindows Azure doesn‘t have durable NTFS file systemNo write access to the application directoryApplication must be statelessSQL Azure – little bit different databaseWindows authenticationDifferences in developmentAzure SDKs
- 3. What Kentico CMS needs to run on AzureKentico CMS 5.5 R2:Windows Azure compute services (ASP.NET web role)Optionally Windows Azure storage (blob storage)SQL AzureASP NET Web roleSQL AzureAzurestorage
- 4. Durable NTFS file system is missingBlob storage is manipulated by special API, two options: Use Azure drive – mount blob storage as NTFS file system, limited for Read/Write to one instance (Kentico CMS 5.5 R2)
- 5. Use blob API directly – code changes needed, no limitations (Kentico CMS 6.0)No write access to application directoryCurrent situation:You shouldn‘t write anything to application directorySome operations are allowed, most of them aren‘tData between instances aren‘t synchronizedInstance data aren‘t durableProblems from KenticoCMS point of view:Modules: Web analytics, Smart search (solved using Azure drive)Database installImport/Export
- 6. Application must be statelessInstance 1 Multi VMs environment
- 8. Round robin algorithmInstance 2Load balancerChallengesSynchronization of memory objectsStoring of session state dataSolutionWeb farms module (6.0)Use Azure session state providerInstance 3
- 9. Application must be statelessOn-premise session state providersAzure session state providers
- 10. SQL Azure – little bit different databaseFew general differences:Main difference – SQL is relation database without additional features (Reporting services, integration services, ...).Reporting services are now in CTPMissing fulltext supportEvery table needs to have at least one clustered indexFrom Kentico CMS point of view:No problem, question of changing connection stringSQL migration wizard, http://sqlazuremw.codeplex.com/
- 11. Windows authenticationIntegrated Windows authentication doesn‘t work with ASP.NET web roleWebDAV integration needs this type of authenticationPossible solution – Windows Azure Connect
- 12. Differences in developmentApplication which run under ASP.NET web role must be Web application projectKentico CMS 5.5 R2 – web site projectNew type of project, new configuration files
- 13. Azure SDKsMultiple versionsKentico 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 CMSSDK 1.3 and upper – Visual studio 2010 needed, issue with running Kentico CMS under full IIS in Visual studio – bug in SDK
- 14. Q&A?
- 15. Thank you! E-mail: dominikp@kentico.com Twitter: DominikPinter Blog: http://devnet.kentico.com/Blogs/Dominik-Pinter.aspx