Presentation at Interop Las Vegas 2008 on the pitfalls of moving to software-as-a-service

3. This man is better at your job than you are.

4. Others have resisted change.

5. A history lesson.

6. 1890: Factories near rivers.

7. 1890: Factories near rivers.

8. 1900: Electrical generators.

9. In just ten years…

10. 1910: Electricity as a utility.

11. 1920: All about the appliances.

12. “ I’m in oven technology.”

16. Everything old is new again. =

24. 2010: Utility computing.

25. Yes, this is going to happen faster than you expect.

29. Why Amazon is better than you. (Werner Vogels at NGN’07)

30. Buy 10,000 computers at a time.

31. Spread load around the world, throughout the day, across the year.

32. Get HA and DR for free.

33. Obsessed with making IT productive.

34. Consumption-based cost tracking built in.

35. Developers devoted to building dynamic capacity management tools.

36. GOOG even builds its own switches!

37. (Oh, and Google’s hosted services are free. )

38. Seriously.

39. “ I’ve got one word for you, boy. Just one word.”

40. Appliances. =

41. The appliance of computing is SaaS.

42. The evolution of computing (with apologies to Forrester) ISP 1.0 Access to the Internet Cloud Your apps on their dynamic infrastructure SaaS Your users on their Internet app BPaaS Your process in their language ISP 2.0 Access to a server on the Internet Colo Your servers in their cages ASP Your data on their apps on their servers

43. A spectrum of control Cloud Your apps on their dynamic infrastructure SaaS Your users on their Internet app BPaaS Your process in their language Maximum control: The machine is your playground Do whatever Minimum control: Your data in their forms Use their dropdowns Medium control: Your business logic on their platforms Use their coding language

44. Consider Salesforce’s APEX platform

47. So why do we switch?

58. http://www.customware.net/repository/download/attachments/6389868/create-s-control.png

78. Ten nasty questions to ask. (Or, how to get a better price from your SaaS provider.)

79. Can I get all my data from you?

80. Is the code I write to customize it portable?

81. Can you tell me where my servers are?

82. Is the app legally usable from anywhere in the world?

83. What kinds of SLA and availability reports do you have?

84. How do I dispute my bill, and what proof do you have?

85. What privacy guarantees do you have in place?

86. What APIs do you offer, how are they supported, and where are the docs?

87. Can I keep users on an older version while I train them on the new one?

88. Can I back up and restore configurations?

89. Why things bite back. Unforeseen consequences and the cautionary tale of the iron.

96. What might bite back?

97. Infrastructure transparency. We need to see where data lives after all.

98. Portability and dependency. A whole new kind of vendor lock-in.

99. Portfolio management tools. Too many SaaS tools to deal with. {Pics of Bitcurrent’s?}

100. Rogue applications. When it’s costless to turn something up, everyone will.

101. SaaS becomes the middleman. If buyer and seller use the same SaaS, does it become a marketplace?

102. Social networking. Shared apps have shared users.

103. Security. Much easier to do bad things when an account is compromised.

104. Competitive advantage. Don’t SaaS what makes you special. {Fedex}

105. QUESTIONS?

106. Thank You.