Differences Between On Premise And Windows Azure

2,934 views

Published on

What are the main differences between On-premise and Windows Azure? What does it mean for the Kentico CMS running in the Cloud?

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,934
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
22
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Differences Between On Premise And Windows Azure

  1. 1. Differences between On-premise and Windows Azure<br />Dominik Pintér (dominikp@kentico.com), Kentico software<br />
  2. 2. Agenda<br />What Kentico CMS needs to run on Azure<br />Windows Azure doesn‘t have durable NTFS file system<br />No write access to the application directory<br />Application must be stateless<br />SQL Azure – little bit different database<br />Windows authentication<br />Differences in development<br />Azure SDKs<br />
  3. 3. What Kentico CMS needs to run on Azure<br />Kentico CMS 5.5 R2:<br />Windows Azure compute services (ASP.NET web role)<br />Optionally Windows Azure storage (blob storage)<br />SQL Azure<br />ASP NET <br />Web role<br />SQL Azure<br />Azure<br />storage<br />
  4. 4. Durable NTFS file system is missing<br />Blob storage is manipulated by special API, two options:<br /><ul><li> Use Azure drive – mount blob storage as NTFS file system, limited for Read/Write to one instance (Kentico CMS 5.5 R2)
  5. 5. Use blob API directly – code changes needed, no limitations (Kentico CMS 6.0)</li></li></ul><li>No write access to application directory<br />Current situation:<br />You shouldn‘t write anything to application directory<br />Some operations are allowed, most of them aren‘t<br />Data between instances aren‘t synchronized<br />Instance data aren‘t durable<br />Problems from KenticoCMS point of view:<br />Modules: Web analytics, Smart search (solved using Azure drive)<br />Database install<br />Import/Export<br />
  6. 6. Application must be stateless<br />Instance 1<br /><ul><li> Multi VMs environment
  7. 7. Load balancer
  8. 8. Round robin algorithm</li></ul>Instance 2<br />Load balancer<br />Challenges<br />Synchronization of memory objects<br />Storing of session state data<br />Solution<br />Web farms module (6.0)<br />Use Azure session state provider<br />Instance 3<br />
  9. 9. Application must be stateless<br />On-premise session state providers<br />Azure session state providers<br />
  10. 10. SQL Azure – little bit different database<br />Few general differences:<br />Main difference – SQL is relation database without additional features (Reporting services, integration services, ...).<br />Reporting services are now in CTP<br />Missing fulltext support<br />Every table needs to have at least one clustered index<br />From Kentico CMS point of view:<br />No problem, question of changing connection string<br />SQL migration wizard, http://sqlazuremw.codeplex.com/<br />
  11. 11. Windows authentication<br />Integrated Windows authentication doesn‘t work with ASP.NET web role<br />WebDAV integration needs this type of authentication<br />Possible solution – Windows Azure Connect<br />
  12. 12. Differences in development<br />Application which run under ASP.NET web role must be Web application project<br />Kentico CMS 5.5 R2 – web site project<br />New type of project, new configuration files<br />
  13. 13. Azure SDKs<br />Multiple versions<br />Kentico CMS supports SDK 1.1 upper (latest is SDK 1.4)<br />Breaking version – SDK 1.3, full IIS support, remote desktop, ...<br />SDK 1.2 and lower – setting for internal role port is missing – minor issues with Kentico CMS<br />SDK 1.3 and upper – Visual studio 2010 needed, issue with running Kentico CMS under full IIS in Visual studio – bug in SDK<br />
  14. 14. Q&A<br />?<br />
  15. 15. Thank you!<br /> E-mail: dominikp@kentico.com<br /> Twitter: DominikPinter<br /> Blog: http://devnet.kentico.com/Blogs/Dominik-Pinter.aspx<br />

×