Slides I presented at the 2/25/2014 Enterprise Mobility Boston meetup. There are several animated slides that don't make a lot of sense when viewed statically. Contact me on LinkedIn if you would like me to run through it.

1. Mark Eisenberg | February 27, 2014

2. This is ME
• Cloud and mobile strategist
• Developer by background
• Spent 17 years in semiconductor sales most notably
with Intel
• Joined Microsoft in 2006
• Founding member of the US Windows Azure sales team in 2009
• Joined a boutique consulting firm in NYC in 2012
• Plan was to transform the firm in to a cloud and mobile specialist
• Currently in search of my next gig
• LinkedIn.com/in/mheisenberg & @AzureBizAndTech

3. • Definition - a statement of the exact meaning of a word, especially
in a dictionary
• Everyone - every person
• Semantics - the meaning of a word, phrase, or text

4. Some Context
•
•
•
•
•
•
•
•
Was the PC about IT?
Was the Web?
Why do we think cloud is?
Cloud is about enabling smart people to do big
things economically
It’s about solving problems in a better way
Oh by the way…
IT can get value from cloud
Just not using the old ways

6. The Challenge

7. Inactivity
Average
Period
Usage
Compute
Compute
How the Challenge Manifests
Average Usage
Time
Time
Compute
Compute
Time
Average Usage
Average Usage
Time

8. Cloud Solution

9. The Challenge

10. The Solution

11. The Challenge

12. The Solution

13. Cloud
The Definition
Slide 13

14. Essential Characteristics
There are 5

15. On Demand and Self-service

16. Rapidly Elastic

17. Multi-tenancy

18. Metered Services

19. Broad Network Access

20. Deployment Models
There are 4

22. Service Models
There are 3

23. “software as a service”
“platform as a service”
“infrastructure as a service”
Lease rather than buy
Building blocks for cloud apps.
Contrary to hype there is no
difference in how they are used.

24. Key Themes
Services

25. What is a service?

26. What’s in a contract?
What the service does
How the service can be accessed
Where the service can be
accessed

27. How are services
used?
To enable scalability
services should be:
•
•
Stateless
Loosely coupled
SOA: principles of service design / Thomas Erl

28. Key Theme
Design for Failure or Design for Reliability

29. Design Principles
• Assume any component can fail
• Determine risk/cost tradeoffs
• Eliminate single points of failure

30. Key Theme
Definitions Matter

31. One More Time with Feeling!
• Public Private
• IaaS PaaS

32. The Mindset

33. Technology Adoption Lifecycle
Crossing the Chasm: Geoffrey Moore

34. The Questions to Ask
• Do we have a problem that involves scale?
• Capacity
• Geography
• Data
• Do we have a culture that allows us to change
how we solve problems?
• Are we early adopters?

35. Recommended Reading
•
•
•
•
•
•
•
•
•
•
•
•
•
•
http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf
http://csrc.nist.gov/publications/nistpubs/800-146/sp800-146.pdf
http://csrc.nist.gov/publications/nistpubs/800-144/SP800-144.pdf
http://www.cloudave.com/11973/designing-for-failure-some-key-facts/
http://www.cloudave.com/14264/intel-joins-hands-with-academia-for-cloud-computingresearch-2/
http://www.twilio.com/engineering/2011/04/22/why-twilio-wasnt-affected-by-todays-aws-issues/
http://techblog.netflix.com/2010/12/four-reasons-we-choose-amazons-cloud-as.html
http://techblog.netflix.com/2010/12/5-lessons-weve-learned-using-aws.html
http://techblog.netflix.com/2011/04/lessons-netflix-learned-from-aws-outage.html
http://broadcast.oreilly.com/2011/04/the-aws-outage-the-clouds-shining-moment.html
http://highscalability.com/blog/2009/6/27/scaling-twitter-making-twitter-10000-percentfaster.html
http://www.infoq.com/articles/SOACloudPanel
https://plus.google.com/112678702228711889851/posts/eVeouesvaVX
http://www.drdobbs.com/web-development/building-scalable-web-architecture-andd/240142422