Building software is a set of smart choices to meet the needs of your customers and the possibilities of technology. Today’s Web demands that customers have a choice in how they deploy their applications. With over 7,000 websites in 84 countries, Kentico CMS for ASP.Net is delivered as a single code base for use as a cloud, hosted, or on-premise solution. With over 34 out of the box modules and everything built on a SQL Server backend – How did we do it? What tradeoffs did we make? In this session we will answer that question and look at how to build a rich and compelling website using Windows Azure.

1. Kentico CMS: A Case Study in Building for Today’s Web Thom Robbins, Chief Evangelist

2. Agenda What is a CMS? Kentico CMS today Meet our cast Enter the time machine – July 2009 First Steps We made it – Kentico CMS 5.5 R2 Business Perspective T-2 Weeks: Kentico CMS 6 Lessons learned

4. WCM

5. DM

7. For Developers.. Delivered as a Visual Studio project 826,152 lines of code 2,000 specifically for Azure

8. Meet our cast Kentico has 75 employees worldwide All development done in HQ Brno, CZ Development team led by CTO 35+ developers Broken into feature teams Led by Technical Leader Devs, Testers and Writers

10. Azure is just coming to market

12. Installation must be simple

15. Native support – no additional support needed (accelerators suck!)Used parts of Windows Azure ASP.NET Web role Azure storage SQL Azure

17. Windows Azure supports only Web applications

18. New type of project – Cloud service (Conversion or download)

21. No backup/restore – a migration tool must be used to move a DB to the cloud, i.e. SQL Azure Migration wizard - http://sqlazuremw.codeplex.com/Kentico CMS 5.5 R2 – technical details

22. Kentico CMS 5.5 R2 - limitations

23. Business Perspective 15 total sites running in Windows Azure, using SQL Azure Stacked instances (2, each hosting 5+ sites) Over ½ of production sites currently migrated to Windows Azure Review of key applications Postage Ink Emerald Coast Autism Center RDF Associates CED Technical

24. T-2 Weeks:Kentico CMS 6 Kentico CMS 6: Azure 1.5 Support! Multiple instance support Storing files on Windows Azure blob storage ASP NET Web role SQL Azure App fabric cache Azure storage Smart search Worker role

25. Installation

26. Handling multi VMs environment Unknown number of servers Dynamic changes Round robin algorithm Web farm modules Inter-role communication Instance 1 Instance 2 Load balancer Instance 3

28. Blob storage as a replacement

29. CMS.IO – storing data using Blob API

30. Direct links to Blob storage

31. Debug

32. MS SQL -> SQL AzureSystem.IO Kentico CMS business layer Azure blob API CMS.IO ...

33. Other features Smart search: Lucene.NET Smart search worker role Application settings and connection string: Service configuration file Windows Azure AppFabric cache Session state provider Hybrid scenarios Use Azure blob as file storage

34. Lessons Learned Don’t Hurry Think about things Understand how it works Little details matter – especially with Azure Be careful with 3rd party components Learn Azure Keep up with news Azure is stateless Complex Web applications aren’t stateless Azure goes against current web architecture

35. Q&A ?

36. Thank you! E-mail: thomasr@kentico.com Twitter: trobbins Blog: http://devnet.kentico.com/Blogs/thomas-robbins.aspx