1. Full Contact Cloud Architecture
and Design
David S. Linthicum
SVP, Cloud Technology Partners
David.linthicum@cloudtp.com
www.cloudtp.com

2. Abstract
So how does one design and build a cloud computing system? My advice is
that you jump in, grab problem by the throat, and make your cloud-based
architecture and resulting system do your bidding. In this session we’ll cover
the right and wrong ways to leverage, design, and build cloud-based systems
and infrastructure. Going beyond the hype, this includes advice from those
currently in the trenches who make cloud computing work for the Global
2000 and government. The audience is anyone who will soon fight to make
cloud computing work for their clients, employers, and/or investors, and
need to knock it out of the park the first time.

3. Slides available:

4. • @DavidLinthicum
• david.linthicum@cloudtp.com
• www.cloudtp.com
• www.davidlinthicum.com
• www.linkedin.com/in/davidlinthicum
• www.slideshare.net/linthicum
• I Blog for InfoWorld and GigaOM Pro

5. Geek Level
Your Grandparents who
That guy who can convert
are still using AOL
your name to Hex

6. Why You Should Care

7. Most Cloud-Based Systems
are Lacking Architecture

9. Thus, many clouds are not
meeting expectations.

10. The results:
• Inefficient utilization of resources.
• Resource saturation.
• Lack of elasticity and scalability.
• Lack of security and governance.
• Frequent outages.
• Bad or no tenant management.
• Other very bad things.

11. Hitting the Wall

12. Common Mistakes
• Not understanding how to make architectures
scale.
• Not dealing with tenant management issues.
• Not understanding that security is systemic, and
impacts performance.
• Not understanding the proper use of services
(Yes, that means SOA).
• Tossing technology at the problem.
• Listening to the wrong people.

13. The Multitenant
Thing
• No two multitenant
architectures are alike.
• Needs to be effective in the
context of the problem.
• Needs to leverage best
architecture practices.
• Needs to practice isolation and
protection.
“With a multitenant architecture, a software application is
designed to virtually partition its data and configuration so
that each client organization works with a customized virtual
application instance.”
Source: Wikipedia

14. You have some
choices
Source: http://vikashazrati.wordpress.com/2008/06/23/multi-tenancy-explained/

15. ABCs of Multitenancy
Source: Steve Bobrowski
Amazon Machine Images

16. Virtualization is Not
Always a Requirement

17. Types of Cloud
Architecture Patterns
Emerging
• Migration to a Cloud
– Business Systems Complexity
– Infrastructure
• Building on a Cloud
(PaaS)
• Building a Hybrid Cloud
• Building a Cloud
– IaaS
– SaaS
– PaaS

18. Types of Cloud
Architecture Patterns
We’ll focus
We’ll focus
here
here Emerging
• Migration to a Cloud
– Business Systems Complexity
– Infrastructure
• Building on a Cloud
(PaaS)
• Building a Hybrid Cloud
• Building a Cloud
– IaaS
– SaaS
– PaaS

19. General Architecture Patterns to Follow

20. Enterprise Vulnerabilities
Assess your Risks
1. Governance
2. Regulatory Compliance
3. Security & Identity Management
4. Business Continuity
RISK TO ORGANIZATION
2
5. Process and Services 1
6. Data Management 4
9 3
7. System Integration 6
8. Resource Skills & Knowledge 5 7
9. Application Readiness 8
10
10. Network Readiness
COMPLEXITY OF MITIGATING RISK

21. Architecture Roadmap
General Guidance
Build a solid foundation:
Determine business drivers
Understand: data, services, business
processes and system integration points
Design a “cloud-friendly” enterprise
architecture roadmap that leverages
Services Oriented Architecture (SOA)
Determine an integration strategy for
internal and external systems
Outline a migration path for legacy systems
to the new architecture

22. “as-is”

23. “to be”

24. deploy

25. General Rules and
Guidelines
• Focus on the primitives.
– The best clouds are sets of low level services that can be
configured.
• Data services
• Transaction services
• Utility services
• Leverage distributed components that are centrally
controlled.
• Build for tenants, not users.
• Don’t lean too much on virtualization.
• Security and governance are systemic.

26. Use Case: General Business System
Migration to the Cloud

27. The General Idea
• Break the system down to it’s component parts,
understanding each part.
• Rethink the database, it’s typically a mess.
• Rethink the system as sets of services/API, watch the
granularity.
– Data services, transaction services, utility services
• Create a security and governance plan.
• Consider the user interfaces.
• Consider device interfaces.
• Migrate only the components to the cloud that will
provide the best value.

28. Good New/Bad
News
• Good News:
– Most cloud platforms provide the tenant management
features for you.
– Most cloud platforms manage the resources for you.
– The cloud platforms are getting better.
• Bad News:
– Security is still your problem.
– Application and service design is still your problem.
– Testing can be a hassle.
– Watch out for immaturity if standards.

29. Reference
Architecture
Monitoring and Management
Management & Service Governance
Process Management
Rules Management Composites/Portals
(BPMS)
Security & Identity
Transactional Services
Data Services/Abstraction
Data

30. Create the Information
Model
Legacy Ontologies
Legacy Ontologies
Metadata Understand Ontologies
Metadata
Data
Data
Dictionary
External Dictionary
External &
Metadata Understand the Data &
Metadata Metadata
(B2B) Metadata
(B2B)
Data
Data
Catalog
Catalog
Catalog the Data
Information
Information
Model
Model
Build Information Model

31. Data Services/Abstraction
Data

32. Create a Service Model
Data Candidate
Data Candidate
Catalog Services
Catalog Understand Services Services
Services
Services
And
Information And
Information
Information
Model
Model
Information to Services Information
Service
Service
Model
Model
Build Service Model

33. Transactional Services
Data Services/Abstraction
Data

34. Source: Microsoft

35. Source: Microsoft

36. Create a Process Model
Data Candidate
Data Candidate
Catalog Processes
Catalog Understand Processes Processes
Services to
Services to
Processes
Information Processes
Information
Model
Model
Services to Processes
Process
Process
Model
Model
Service Build Process Model
Service
Model
Model

37. Monitoring and Management
Process Management
Rules Management Composites/Portals
(BPMS)
Transactional Services
Data Services/Abstraction
Data

38. Source: Activevos

39. Create a Governance Model
Process Defined
Process Defined
Model Policies
Model Define Policies Policies
Policy
Policy
Designs
Information Designs
Information
Model
Model
Design Policies
Governance
Governance
Model
Model
Service Implement Policies
Service
Model
Model

40. Monitoring and Management
Management & Service Governance
Process Management
Rules Management Composites/Portals
(BPMS)
Security & Identity
Transactional Services
Data Services/Abstraction
Data

42. Policies
Policies
Runtime
Governance
Monitoring
Repository Logs

43. Assigning Candidate Data,
Services, and
Processes for the Clouds
Process
Candidate Process
Assignments
Candidate
Processes Analyze Candidate Processes
Assignments
Processes
Service
Service
Assignments
Assignments
Candidate
Candidate Analyze Candidate Services
Services
Services
Data
Data
Assignments
Assignments
Data Analyze Candidate Data
Data
Dictionary
Dictionary
and
and
Metadata
Metadata
Governance
Governance
Model
Model

44. Select Platforms and Deploy
Processes, Services, and Data
to Platforms.
Candidate
Candidate
Platforms
Process
Process List Candidate Platforms Platforms
Assignments
Assignments
Test
Test
Results
Service Results
Service
Assignments Analyze and Test
Assignments
Candidate Platforms
Target
Target
Platforms
Data Platforms
Data
Assignments
Assignments Select Target Platforms
Deploy to
Target Platforms

45. Stepping to the
Clouds

46. Q&A

47. Thanks!