5. 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.
6. Common Mistakes
• Not understanding how to make architectures scale.
• Not dealing with tenant management issues.
• Not understanding that security is systemic.
• Not understanding the proper use of services.
• Tossing technology at the problem.
• Listening to the wrong people.
• Managing-by-magazine.
7. 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
11. Types of Cloud Architecture Patterns Emerging
• Migration to a Cloud
• Business Systems
• Infrastructure
Complexity
• Building on a Cloud (PaaS)
• Building a Hybrid Cloud
• Building a Cloud
• IaaS
• SaaS
• PaaS
13. Enterprise Vulnerabilities Assess your Risks
1. Governance
2. Regulatory Compliance
3. Security & Identity Management
• RISK TO ORGANIZATION
4. Business Continuity
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
Assess your vulnerabilities and mitigate your risks.
•
14. Architecture Roadmap Where to begin
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
Leverage SOA to build a sturdy and agile foundation for the Cloud
•
18. 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.
19. Where To Find Out More
Slides available:
Bonus Content: How to architect a hybrid cloud computing solution.
