Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Full contact cloud architecture and design linthicum ver 2


Published on

Full contact cloud architecture and design linthicum ver 2

  1. 1. Full Contact Cloud Architecture and Design David S. Linthicum SVP, Cloud Technology Partners
  2. 2. AbstractSo how does one design and build a cloud computing system? My advice isthat you jump in, grab problem by the throat, and make your cloud-basedarchitecture and resulting system do your bidding. In this session we’ll coverthe right and wrong ways to leverage, design, and build cloud-based systemsand infrastructure. Going beyond the hype, this includes advice from thosecurrently in the trenches who make cloud computing work for the Global2000 and government. The audience is anyone who will soon fight to makecloud computing work for their clients, employers, and/or investors, andneed to knock it out of the park the first time.
  3. 3. Slides available:
  4. 4. • @DavidLinthicum•••••• I Blog for InfoWorld and GigaOM Pro
  5. 5. Geek LevelYour Grandparents who That guy who can convert are still using AOL your name to Hex
  6. 6. Why You Should Care
  7. 7. Most Cloud-Based Systemsare Lacking Architecture
  8. 8. Thus, many clouds are not meeting expectations.
  9. 9. 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.
  10. 10. Hitting the Wall
  11. 11. 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.
  12. 12. 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
  13. 13. You have some choicesSource:
  14. 14. ABCs of Multitenancy Source: Steve BobrowskiAmazon Machine Images
  15. 15. Virtualization is NotAlways a Requirement
  16. 16. 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
  17. 17. 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
  18. 18. General Architecture Patterns to Follow
  19. 19. Enterprise Vulnerabilities Assess your Risks1. Governance2. Regulatory Compliance3. Security & Identity Management4. Business Continuity RISK TO ORGANIZATION 25. Process and Services 16. Data Management 4 9 37. System Integration 68. Resource Skills & Knowledge 5 79. Application Readiness 8 1010. Network Readiness COMPLEXITY OF MITIGATING RISK
  20. 20. Architecture Roadmap General GuidanceBuild a solid foundation:Determine business driversUnderstand: data, services, business processes and system integration pointsDesign a “cloud-friendly” enterprise architecture roadmap that leverages Services Oriented Architecture (SOA)Determine an integration strategy for internal and external systemsOutline a migration path for legacy systems to the new architecture
  21. 21. “as-is”
  22. 22. “to be”
  23. 23. deploy
  24. 24. 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.
  25. 25. Use Case: General Business SystemMigration to the Cloud
  26. 26. 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.
  27. 27. 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.
  28. 28. Reference Architecture Monitoring and ManagementManagement & Service Governance Process Management Rules Management Composites/Portals (BPMS) Security & Identity Transactional Services Data Services/Abstraction Data
  29. 29. Create the Information ModelLegacy Ontologies Legacy OntologiesMetadata Understand Ontologies Metadata Data Data DictionaryExternal 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
  30. 30. Data Services/Abstraction Data
  31. 31. Create a Service ModelData Candidate Data CandidateCatalog Services Catalog Understand Services Services Services Services AndInformation And Information InformationModel Model Information to Services Information Service Service Model Model Build Service Model
  32. 32. Transactional ServicesData Services/Abstraction Data
  33. 33. Source: Microsoft
  34. 34. Source: Microsoft
  35. 35. Create a Process ModelData Candidate Data CandidateCatalog Processes Catalog Understand Processes Processes Services to Services to ProcessesInformation Processes InformationModel Model Services to Processes Process Process Model ModelService Build Process Model ServiceModel Model
  36. 36. Monitoring and ManagementProcess Management Rules Management Composites/Portals (BPMS) Transactional Services Data Services/Abstraction Data
  37. 37. Source: Activevos
  38. 38. Create a Governance ModelProcess Defined Process DefinedModel Policies Model Define Policies Policies Policy Policy DesignsInformation Designs InformationModel Model Design Policies Governance Governance Model ModelService Implement Policies ServiceModel Model
  39. 39. Monitoring and ManagementManagement & Service Governance Process Management Rules Management Composites/Portals (BPMS) Security & Identity Transactional Services Data Services/Abstraction Data
  40. 40. Policies Policies Runtime Governance MonitoringRepository Logs
  41. 41. Assigning Candidate Data, Services, and Processes for the Clouds ProcessCandidate Process Assignments CandidateProcesses Analyze Candidate Processes Assignments Processes Service Service Assignments AssignmentsCandidate Candidate Analyze Candidate ServicesServices Services Data Data Assignments AssignmentsData Analyze Candidate Data DataDictionary Dictionaryand andMetadata MetadataGovernance GovernanceModel Model
  42. 42. Select Platforms and Deploy Processes, Services, and Data to Platforms. Candidate Candidate PlatformsProcess Process List Candidate Platforms PlatformsAssignments Assignments Test Test ResultsService Results ServiceAssignments Analyze and Test Assignments Candidate Platforms Target Target PlatformsData Platforms DataAssignments Assignments Select Target Platforms Deploy to Target Platforms
  43. 43. Stepping to the Clouds
  44. 44. Q&A
  45. 45. Thanks!