• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Differences Between On Premise And Windows Azure
 

Differences Between On Premise And Windows Azure

on

  • 1,955 views

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

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

Statistics

Views

Total Views
1,955
Views on SlideShare
1,955
Embed Views
0

Actions

Likes
0
Downloads
18
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Differences Between On Premise And Windows Azure Differences Between On Premise And Windows Azure Presentation Transcript

    • Differences between On-premise and Windows Azure
      Dominik Pintér (dominikp@kentico.com), Kentico software
    • 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
    • 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
    • Durable NTFS file system is missing
      Blob 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)
      • Use blob API directly – code changes needed, no limitations (Kentico CMS 6.0)
    • No write access to application directory
      Current situation:
      You shouldn‘t write anything to application directory
      Some operations are allowed, most of them aren‘t
      Data between instances aren‘t synchronized
      Instance data aren‘t durable
      Problems from KenticoCMS point of view:
      Modules: Web analytics, Smart search (solved using Azure drive)
      Database install
      Import/Export
    • Application must be stateless
      Instance 1
      • Multi VMs environment
      • Load balancer
      • Round robin algorithm
      Instance 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
    • Application must be stateless
      On-premise session state providers
      Azure session state providers
    • 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/
    • 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
    • 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
    • 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
    • Q&A
      ?
    • Thank you!
      E-mail: dominikp@kentico.com
      Twitter: DominikPinter
      Blog: http://devnet.kentico.com/Blogs/Dominik-Pinter.aspx