5 things you need to know about Windows Azure


Published on

Are you taking Kentico CMS to the Windows Azure cloud? What’s important to know? In this webinar Dominik Pinter, Kentico CMS Senior Developer, covers the top five things everyone should know when running Kentico CMS in the cloud.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

5 things you need to know about Windows Azure

  1. 1. 5 things you need to know about Windows Azure<br />Dominik Pinter, dominikp@kentico.com<br />
  2. 2. Five key points<br />What is Windows Azure<br />Architecture differences between on-premise and Microsoft cloud<br />Workflow<br />Windows Azure challenges<br />Where to find best information<br />
  3. 3. What is Windows Azure<br />1<br />
  4. 4. What is Windows Azure<br />Cloud computing service from Microsoft<br />Combination of PaaS and IaaS<br />New development platform<br />
  5. 5. Windows Azure as part of Windows Azure<br /> SQL Azure<br /> Windows Azure<br />Compute<br />Database <br />SQL reporting<br />Storage<br />Networking<br /> Windows Azure market<br /> Windows Azure <br /> App farbric<br />Data market<br />Service bus<br />Access control<br />Application market<br />Cache<br />
  6. 6. Architecture differences<br />2<br />
  7. 7. Architecture differences<br />What is the same: <br /><ul><li>ASP.NET application runs on IIS
  8. 8. All applications run on Windows server
  9. 9. Application uses SQL server or another type of storage for data
  10. 10. Development is still done with Visual studio</li></ul>Main differences:<br /><ul><li>Application consists of parts called roles
  11. 11. There is no persistent/durable virtual machine
  12. 12. There is no persistent/durable NTFS file system
  13. 13. Application runs in multi instance (server) environment
  14. 14. New API, new configuration files, new type of project</li></li></ul><li>Architecture differences - replacements<br />On-premise -> Off-premise (cloud):<br />Server with IIS -> Windows Azure compute service<br />ASP.NET web application -> Windows Azure web role<br />Desktop application/Win service -> Windows Azure worker role<br />NT file system -> Azure blob storage<br />Windows SQL Server -> SQL Azure<br />Memory storage -> Windows Azure Appfabric cache<br />Things for easy migration:<br /><ul><li>Windows Azure drive
  15. 15. Admin mode
  16. 16. Startup tasks
  17. 17. VM role
  18. 18. Full IIS</li></li></ul><li>Picking your CMS Architecture<br /><ul><li>Kentico CMS is Windows Azure ready
  19. 19. Main idea: „Customer will not see difference between on-premise and off-premise“
  20. 20. Support of mixed solutions</li></ul>Single Installation<br />Requirements<br />Growth<br />Cloud<br />Mixed<br />Split your installation<br />Own your installation<br />
  21. 21. Kentico CMS – architecture overview<br /><ul><li>Kentico CMS uses „replacements“
  22. 22. Every part could be mixed</li></ul>AppFabric<br />cache<br />ASP.NET <br />Web role<br />SQL Azure<br />Azure<br />storage<br />
  23. 23. Workflow<br />3<br />
  24. 24. Workflow<br />Special account – authorization based on Live ID identity, only 1 global admin<br />Payment – credit card, pay as you go model<br />Management portal – service management, application deployment, certification management<br />Automatization – powershell, Service management API<br />Development and testing on emulator<br />Deployment to staging environment<br />Run in production environment<br /><ul><li> Compute + storage
  25. 25. Not same as real cloud
  26. 26. Necesary for development
  27. 27. Testing in real cloud
  28. 28. Costs same as production
  29. 29. Portal, Visual studio, powershell, API, ...
  30. 30. Swap
  31. 31. Put service down or lose data?</li></li></ul><li>Challenges<br />4<br />
  32. 32. Challenges<br />Don‘t need to worry about:<br />CPU, Memory, storage, ...<br />Need to solve:<br />Running in multi VM environment<br />How/where to store application state<br />How/where to store application data<br />
  33. 33. Multi VM environment and our solution<br />Instance 1<br />Windows Azure:<br /><ul><li> Multi VM environment
  34. 34. Load balancer
  35. 35. 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 />1. Current: 1 instance support<br /> Next: improved web farms module<br />Current: InProc session state provider<br />Next: Appfabric cache session state provider<br />Instance 3<br />
  36. 36. Data storage and our solution<br />Both versions : Storing files into SQL Azure -> expensive solution<br />Current version:<br /><ul><li>Modules store their data into SQL Azure
  37. 37. Smart search, media library and web analytics modules store their data into Blob storage using Azure drive</li></ul>Next version:<br /><ul><li> Modules can store data into SQL Azure or to blob storage using CMS.IO</li></ul>System.IO<br />Kentico CMS<br />business <br />layer<br />Azure blob API<br />CMS.IO<br />...<br />
  38. 38. Where to find best information<br />5<br />
  39. 39. Where to find best information<br />Windows Azure in general:<br />Every half year new update => need to learn new things<br />Windows Azure platform training kit<br />http://www.windowsazureblog.com/<br />Microsoft conferences – Mix, PDC, ...<br />Windows Azure and Kentico CMS:<br />Our devnet portal: http://devnet.kentico.com<br />Azure deployment guide<br />Kentico webinars<br />
  40. 40. Q&A<br />?<br />
  41. 41. Thank you!<br /> E-mail: dominikp@kentico.com<br /> Twitter: DominikPinter<br /> Blog: http://devnet.kentico.com/Blogs/Dominik-Pinter.aspx<br />