Deze sessie geeft een duidelijk beeld over een nieuwe stroming in de IT-wereld: Cloud Computing. Beginnen doen we met een globaal beeld van wat deze nieuwe technologie te bieden heeft en hoe deze zich verhoudt tot “traditionele” infrastructuur en ontwikkeling. Daarna wordt de focus verlegd naar Microsoft’s implementatie van Cloud Computing: Windows Azure. Gecombineerd met een aantal praktijkvoorbeelden zal deze sessie de mist rond Cloud Computing uitklaren.

2. Cloud Computing & Windows Azure Lessius Hogeschool, Mechelen Maarten Balliauw – RealDolmenE-mail: maarten.balliauw@realdolmen.comBlog: http://blog.maartenballiauw.beTwitter: @maartenballiauw

3. Who am I? Maarten Balliauw Antwerp, Belgium www.realdolmen.com Technology Specialist Windows Azure Co-founder of AZUG Focus on web ASP.NET, ASP.NET MVC, PHP, Azure, … MVP ASP.NET http://blog.maartenballiauw.be @maartenballiauw

4. Agenda Cloud Computing Microsoft Cloud & Windows Azure Some examples A Payroll Company Chronorace Conclusion

5. Cloud Computing What is cloud computing?

6. Inefficiencies in traditional IT… Allocated IT-capacities Load Forecast “Under-supply“ of capacities “Waste“ of capacities Fixed cost of IT-capacities IT CAPACITY Barrier for innovations ActualLoad TIME

7. However, in a Cloud View Load Forecast Allocated IT capacities No “under-supply“ IT CAPACITY Reduction of “over-supply“ Possible reduction of IT-capacities in case of reduced load Reduction of initial investments ActualLoad Time

8. three types of clouds Off Premises On Premises Location Homogeneous Heterogeneous Infrastructure Choices Choices CapEx (invest) OpEx (cost) Business model Own Lease/Rent Ownership Self Third Party Management Self Third Party Responsibilities Customized Standardized Standardization Private Dedicated / Shared Shared Private Dedicated / Shared Shared

9. IT as a Service – Types of services Scalability Customisation Management and responsibilities by vendor In-house management, responsibilities, ...

11. Over provisioned capacity is wasted

12. Time to market can be cumbersome

13. Successful services needs to grow/scale

14. Keeping up w/ growth is big IT challenge

16. Sudden spike impacts performance

17. Can’t over provision for extreme cases

18. Services with micro seasonality trends

19. Peaks due to periodic increased demand

20. IT complexity and wasted capacity Typical workload patterns that benefitfrom a cloud model

21. And of course one more...

22. Horseless Carriage Syndrome Early 20th century: “car” Long standing paradigm: “horse and carriage” Initial failure to comprehend the new paradigm “The horse is here to stay but the automobile is only a novelty“ High cost and shortage of capable drivers Engineers kept designing the whip holder First cars looked alike However... Technology evolved Faster time to “market” (horses get tired) Reduction in complexity and cost No need to care for a horse

23. Mindswitches – Business perspective Investments become costs CapEx vs. OpEx Difficult to work with fixed budgets* Cloud is cheap in many cases You rent capacity, not servers Management is automated IT staff will have other work to do More innovation IT department can be bypassed for quick PoCs Low entry costs = lower barrier for innovation New ways of generating revenue

24. Mindswitches – IT staff Your job will look different (a little) No more server re-imaging* Less server management Monitoring of applications, not servers Architecture of IT becomes far more interesting On-premises servers and machines Virtual machines somewhere in the cloud but also domain joined Security LAN/WAN capacity / interconnectivity Provisioning

25. Mindswitches – Developers Architecture becomes far more interesing Storage can be different depending on your needs Databases can be different depending on your needs Loosely coupled applications Think big It’s a Windows world Proof of concepts Why not bypass IT for PoCs if you can just fire up a new subscription?

26. Microsoft Cloud Overview of all platform components

27. Birds-eye overview Online SaaS PaaS IaaS Customer Relation Management xRM ... E-mail Social networking Blogging Photos Office online SkyDrive Live Mesh ... Reporting Connectivity Access control Compute Storage Management Content Delivery Network Relational Database Reporting Synchronization Connectivity Service bus Authentication Federation Relational data Management Compute Storage Flexible APIs Flexible APIs Management Information Marketplace Information Marketplace Reporting & BI Connect Billing & Payments Data Sync

28. Technology support on Windows Azure Supported by Microsoft: .NET stack PHP Java Ruby Not supported yet working smoothly: MySQL Memcached Jetty (alternative JAVA server) …

29. North America Region Asia Pacific Region Europe Region N. Europe Sub-region N. Central – US Sub-region E. Asia Sub-region W. Europe Sub-region S. Central - US Sub-region S.E. Asia Sub-region

36. EXAMPLE CASES Some example cases

37. A PayRoll Company An example...

38. A Payroll Company Delivering payroll services to other companies General payroll services, staffing, tax, legal, ... Many processes not automated Continuously on the look to automate processes and interaction with clients and their employees

39. Their project: Compensations à la Carte Allow customers to use their software Allow customers to plug in different services Allow employees of customers to select their compensations

40. What’s in the cloud? The problem… Compensations à la Carte

41. Some issues... Will it work? What will it cost with 1 customer and 50 employees? What will it cost with 100 customers and 1000 employees? What if all customers sign up and we have 100.000 employees? And what about the interaction with other services? Uncertainty! Development costs will be fixed Infrastructure costs... Maybe low, maybe high?

42. Cloud allows innovation! Development costs will be there Infrastructure costs will increase when revenue increases Cloud is a perfect fit to drive innovation!

43. ChronoRace An example... FirstWindows Azure implementation in Belgium!

44. ChronoRace Delivering infrastructure for timing sports events Running, biking, triathlon, mountainbike, … Founded 10 years ago, Malmédy, 4 persons Timing of every participant Video footage of every participant PDF certificates for every participant Around 340 events per year! Belgium, Luxemburg, France, Germany, Netherlands, … Small events Large events Dwars door Brugge 8.000 participants Antwerp 10 Miles 17.000 participants 20km of Brussels 30.000 participants

45. ChronoRace – Revenue Revenue generated from “Timing-as-a-Service” Video advertising

46. What’s in the cloud? The problem… Big events are fun, but also

47. Google Analytics fromAntwerp 10 Miles 2010

48. Big event… 20km through Brussels > 30.000 participants Downloading their certificate 30.000 hits processing a PDF Watching results online 30.000 hits* Having a video online 30.000 x +/- 10MB (= 292 GB) Watching their video 30.000 video views? And showing off to family and friends… 30.000 x 10MB x 10 views (avg.) = 2,92 TB bandwidth in 1 day About 35 Mbps Over a 10 Mbps line…

50. What’s in the cloud? Possible solutions What are the options?

51. Possible solutions Current solution: traffic spread Other options Invest in infrastructure Migrate to a cloud model

52. Invest in infrastructure Current infrastructure Leased hardware at a hoster 10 Mbps Internet connection 1 web server (XEON, 2 GB RAM), IIS6 1 database server (XEON, 2 GB RAM), SQL Server 2005 “What-if” infrastructure Leased hardware at a hoster 10 Mbps Internet connection 5 web server (XEON, 2 GB RAM), IIS6 1 database server (XEON, 2 GB RAM), SQL Server 2005

53. Migrate to a cloud model “What-if” cloud model Windows Azure Storage Windows Azure compute (1 instance ~ 15 days) Windows Azure compute (5 instances ~ 15 days) SQL Azure Business Edition Equivalent of 10 Mbps bandwidth

54. Economics

55. Other indicators Workload Variable workload, predictable Business Availability has direct impact on revenue Offering as a service No system engineers: developer currently maintaininginfrastructure Data Large amount of data storage for short periods

56. Issues identified Technical Application written in VS2005 Third-party component is 32bit only Amount of traffic =~ 3 TB on 1 day Deployment Non-technical Third-party component licensing per-server All employees busy on event  no time for intervention

57. Conclusion Large economic benefit Less costs, more capacity ~ more revenue Clear indicators for cloud model Some minor issues detected An almost perfect cloud fit

58. What’s in the cloud? Implementing the Solution Let’s go Windows Azure!

59. Step 1: Migrate tools VS2005 Web Site project Migrate to VS2010 Migration took some time Add namespaces Restructure classes Throw out stuff that was no longer used Migration allowed us to get a cleaner application

60. Step 2: Database Current database size: around 2,5 GB Squeeze stuff into 1 GB? Data retention Restructure database? Use multiple databases?* *future proved this would probably be better

61. Step 2: Database Decided to go for 10 GB version Migration Using open source: SQL Azure Migration Wizardhttp://sqlazuremw.codeplex.com Worked surprisingly good! 2 stored procedures could not be migrated

62. Step 2: Database 1 week after project start Current website at www.chronorace.be with SQL Azure backend As easy as changing the connection string! Cloud is not all-or-nothing

63. Step 3: Streaming Currently a Flash player Downloads chunks of +/- 1 MB Should work on blob storage! Cheap storage Cheap traffic CDN support API supports downloading chunks

64. Step 3: Streaming Getting a specific chunck was variable in response time Decided to cache the video to compute web roles During the advert that is shown Next view of the video is instant! Option for the future: Silverlight & IIS Smooth Streaming

65. Step 4: Deployment Site is +/- 300 MB, deploy this every time? Deployment through portal seems to take forever Uploading 300 MB for a very small change is crazy We decided to move images and static content to blob storage and serve it fromthere Code and dynamic content are on Windows Azure. Making it a 3,5 MB application.

66. Step 5: Scaling Done by doing this: Would be awesome to have this: Not possible! “When” should it scale? “How” should it scale? “Who” / “What” is responsible for scaling? <Instancescount="2" /> <InstancesminInstances="3" maxInstances="10" />

67. Step 5: Auto Scaling Auto scaling would be a big benefit During events all 4 people are busy It is the cloud after all? The scale-up/down thing? Application should be able to monitor itself RealDolmen auto scaling component

68. Auto Scaling – Scaling logic Scaling logic provider uses sensor data to suggest an action (up/fast-up/down/stable) To implement per application Just a suggestion! Scaling logic provider uses sensor data to suggest an action (up/fast-up/down/stable) To implement per application Just a suggestion!

69. Step 5: Auto Scaling in ChronoRace Sensor based on concurrent video streams Scales between 2 and 20 instances automatically Hard to verify! The Windows Azure portal is not willing to disclose the number of instances during scale. MMC Snap-In does give useful info!http://code.msdn.microsoft.com/windowsazuremmc

70. Step 5: Auto Scaling in ChronoRace 20km through Brussels 7 instances on average, 18 in peak

71. What’s in the cloud? Conclusion Was it a good move?

73. Would have crashed

74. Ad revenue impact 

75. Price is moderate

76. All requests served

78. ChronoRace summary Pitfalls were identified during Windows Azure Assessment Most hours spent with VS2005 - VS2010 migration 20km through Brussels event survived RealDolmen auto scaling component Leverage the platform Benefit from Scale vs. Economics

79. Takeaways What to remember?

80. What to remember? Cloud is not all-or-nothing Windows Azure is Operating system (computing & storage) SQL Azure AppFabric (= integration) Cloud is notall-or-nothing Quick wins On and Off Scale fast, fail fast Peak scenarios

81. AZUG.BE – Azure User Group Belgium Focus on the Azure Services Platform Community driven Focus on architecture And development And the business value of Azure

82. Thankyou … … foryourattention ! … for the invitation ! Maarten Balliauwhttp://blog.maartenballiauw.be