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.

How to Get Cloud Architecture and Design Right the First Time

16,126 views

Published on

Published in: Technology, Business
  • I am surprised - a few years ago separation between process layer and service layer was excusable. In 2012, it is time to understand that a process is an implementation of the service, and the service is a provider for another process - they are mixed.

    I have not found in the presentation any concerns specific to Clouds that are not already known for services (SO architecture).
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • I am surprised - a few years ago separation between process layer and service layer was excusable. In 2012, it is time to understand that a process is an implementation of the service, and the service is a provider for another process - they are mixed.

    I have not found in the presentation any concerns specific to Clouds that are not already known for services (SO architecture).
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

How to Get Cloud Architecture and Design Right the First Time

  1. 1. David S. Linthicum Blue Mountain Labs [email_address] How to Get Cloud Architecture and Design Right the First Time
  2. 2. Abstract <ul><li>So, what are the proper ways to design, build, and leverage cloud computing systems? What are the steps to success? What are the emerging best practices? How does SOA fit in? In this session we’ll answer these questions, and more, covering 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. </li></ul>
  3. 3. Where To Find Out More Bonus Content: How to architect a hybrid cloud computing solution. Slides available:
  4. 4. Where to find me. <ul><li>@DavidLinthicum </li></ul><ul><li>[email_address] </li></ul><ul><li>www.bluemountainlabs.com </li></ul><ul><li>www.davidlinthicum.com </li></ul><ul><li>http://www.linkedin.com/in/davidlinthicum </li></ul><ul><li>Grab a card after the presentation. </li></ul>
  5. 5. Geek Level for this Presentation Systems Programmer and Dungeon Master Your Grandparents that are Still Using AOL Dialup
  6. 6. <ul><li>Why You Should Care </li></ul>
  7. 7. Most Cloud-Based Systems are Lacking Architecture
  8. 8. The results: <ul><li>Inefficient utilization of resources. </li></ul><ul><li>Resource saturation. </li></ul><ul><li>Lack of elasticity and scalability. </li></ul><ul><li>Lack of security and governance. </li></ul><ul><li>Frequent outages. </li></ul><ul><li>Bad or no tenant management. </li></ul><ul><li>Other very bad things. </li></ul>
  9. 9. Common Mistakes <ul><li>Not understanding how to make architectures scale. </li></ul><ul><li>Not dealing with tenant management issues. </li></ul><ul><li>Not understanding that security is systemic. </li></ul><ul><li>Not understanding the proper use of services. </li></ul><ul><li>Tossing technology at the problem. </li></ul><ul><li>Listening to the wrong people. </li></ul><ul><li>Managing-by-magazine. </li></ul>
  10. 10. The Multitenant Thing <ul><li>No two multitenant architectures are alike. </li></ul><ul><li>Needs to be effective in the context of the problem. </li></ul><ul><li>Needs to leverage best architecture practices. </li></ul><ul><li>Needs to practice isolation and protection. </li></ul>“ 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. 12. The ABCs Multitenancy Source: Lori MacVittie
  12. 13. ABCs of Multitenancy Source: Steve Bobrowski Amazon Machine Images
  13. 14. Virtualization is Not Always a Requirement
  14. 15. Types of Cloud Architecture Patterns Emerging <ul><li>Migration to a Cloud </li></ul><ul><ul><li>Business Systems </li></ul></ul><ul><ul><li>Infrastructure </li></ul></ul><ul><li>Building on a Cloud (PaaS) </li></ul><ul><li>Building a Hybrid Cloud </li></ul><ul><li>Building a Cloud </li></ul><ul><ul><li>IaaS </li></ul></ul><ul><ul><li>SaaS </li></ul></ul><ul><ul><li>PaaS </li></ul></ul>Complexity
  15. 16. <ul><li>General Architecture Patterns to Follow </li></ul>
  16. 17. Enterprise Vulnerabilities Assess your Risks <ul><li>Governance </li></ul><ul><li>Regulatory Compliance </li></ul><ul><li>Security & Identity Management </li></ul><ul><li>Business Continuity </li></ul><ul><li>Process and Services </li></ul><ul><li>Data Management </li></ul><ul><li>System Integration </li></ul><ul><li>Resource Skills & Knowledge </li></ul><ul><li>Application Readiness </li></ul><ul><li>Network Readiness </li></ul>Assess your vulnerabilities and mitigate your risks. COMPLEXITY OF MITIGATING RISK <ul><li>RISK TO ORGANIZATION </li></ul>1 2 5 3 4 6 7 8 9 10
  17. 18. Architecture Roadmap Where to begin <ul><li>Build a solid foundation: </li></ul><ul><li>Determine business drivers </li></ul><ul><li>Understand: data, services, business processes and system integration points </li></ul><ul><li>Design a “cloud-friendly” enterprise architecture roadmap that leverages Services Oriented Architecture (SOA) </li></ul><ul><li>Determine an integration strategy for internal and external systems </li></ul><ul><li>Outline a migration path for legacy systems to the new architecture </li></ul>Leverage SOA to build a sturdy and agile foundation for the Cloud
  18. 19. “ as-is”
  19. 20. “ to be”
  20. 21. deploy
  21. 22. General Rules and Guidelines <ul><li>Focus on the primitives. </li></ul><ul><ul><li>The best clouds are sets of low level services that can be configured. </li></ul></ul><ul><ul><ul><li>Data services </li></ul></ul></ul><ul><ul><ul><li>Transaction services </li></ul></ul></ul><ul><ul><ul><li>Utility services </li></ul></ul></ul><ul><li>Leverage distributed components that are centrally controlled. </li></ul><ul><li>Build for tenants, not users. </li></ul><ul><li>Don’t lean too much on virtualization. </li></ul><ul><li>Security and governance are systemic. </li></ul>
  22. 23. <ul><li>Use Case: General Business System Migration to the Cloud </li></ul>
  23. 24. The General Idea <ul><li>Break the system down to it’s component parts, understanding each part. </li></ul><ul><li>Rethink the database, it’s typically a mess. </li></ul><ul><li>Rethink the system as sets of services/API, watch the granularity. </li></ul><ul><ul><li>Data services, transaction services, utility services </li></ul></ul><ul><li>Create a security and governance plan. </li></ul><ul><li>Consider the user interfaces. </li></ul><ul><li>Consider device interfaces. </li></ul><ul><li>Migrate only the components to the cloud that will provide the best value. </li></ul>
  24. 25. Good New/Bad News <ul><li>Good News: </li></ul><ul><ul><li>Most cloud platforms provide the tenant management features for you. </li></ul></ul><ul><ul><li>Most cloud platforms manage the resources for you. </li></ul></ul><ul><ul><li>The cloud platforms are getting better. </li></ul></ul><ul><li>Bad News: </li></ul><ul><ul><li>Security is still your problem. </li></ul></ul><ul><ul><li>Application and service design is still your problem. </li></ul></ul><ul><ul><li>Testing can be a hassle. </li></ul></ul>
  25. 26. Reference Architecture Security & Identity Management & Service Governance Data Data Services/Abstraction Transactional Services Process Management (BPMS) Composites/Portals Monitoring and Management Rules Management
  26. 27. Create the Information Model Ontologies Understand Ontologies Understand the Data Data Dictionary & Metadata Catalog the Data Data Catalog Legacy Metadata External Metadata (B2B) Build Information Model Information Model
  27. 28. Reference Architecture Data Data Services/Abstraction
  28. 29. Create a Service Model Candidate Services Understand Services Information to Services Services And Information Build Service Model Service Model Data Catalog Information Model
  29. 30. Reference Architecture Data Data Services/Abstraction Transactional Services
  30. 31. Cloud Provider On Premises
  31. 32. Cloud Provider On Premises
  32. 33. Create a Process Model Candidate Processes Understand Processes Services to Processes Services to Processes Build Process Model Process Model Data Catalog Information Model Service Model
  33. 34. Reference Architecture Data Data Services/Abstraction Transactional Services Process Management (BPMS) Composites/Portals Rules Management
  34. 35. On Premises Cloud Provider
  35. 36. Create a Governance Model Defined Policies Define Policies Design Policies Policy Designs Implement Policies Governance Model Process Model Information Model Service Model
  36. 37. Reference Architecture Security & Identity Management & Service Governance Data Data Services/Abstraction Transactional Services Process Management (BPMS) Composites/Portals Monitoring and Management Rules Management
  37. 38. Runtime Governance Repository Logs Policies Policies Monitoring
  38. 39. Test SOA using Cloud Architecture Test Plan Create Test Plan Black Box Testing Black Box Testing Results White Box Testing White Box Testing Results Process Model Information Model Service Model Governance Model
  39. 40. Assigning Candidate Data, Services, and Processes for the Clouds Process Assignments Analyze Candidate Processes Analyze Candidate Services Service Assignments Analyze Candidate Data Data Assignments Candidate Processes Candidate Services Data Dictionary and Metadata Governance Model
  40. 41. Select Platforms and Deploy Processes, Services, and Data to Platforms. Candidate Platforms List Candidate Platforms Analyze and Test Candidate Platforms Test Results Select Target Platforms Target Platforms Process Assignments Service Assignments Data Assignments Deploy to Target Platforms
  41. 42. Data Data Data Data Data Services Processes
  42. 43. Data Data Data Data Data Services Processes PaaS IaaS DaaS
  43. 44. Data Data Data Data Data Services Processes PaaS IaaS DaaS Application Application
  44. 45. Stepping to the Clouds
  45. 46. <ul><li>Q&A </li></ul>
  46. 47. We are leading the conversation with thought leadership and cutting edge services. The shift to Cloud #1 best selling book on Cloud Computing #1 Most read blog on Cloud Computing #1 Most listened to Podcast on Cloud Computing with over 10,000 listeners
  47. 48. <ul><li>Additional Slides </li></ul>
  48. 49. <ul><li>Use Case: Creating an Hybrid Cloud </li></ul>
  49. 50. Current Patterns: Primitive Hybrid Architectures Public Cloud Private Cloud API/Services Migration Interoperability Public Cloud Private Cloud
  50. 51. Best: Cloud Abstraction Private Cloud B Public Cloud C Private Cloud A Abstraction Layer (Composite)
  51. 52. Emerging Hybrid Cloud Architectural Patterns <ul><li>Static Placement </li></ul><ul><li>Assisted Replication </li></ul><ul><li>Auto Migration </li></ul><ul><li>Dynamic Migration </li></ul><ul><li></li></ul>
  52. 53. Static Placement <ul><li></li></ul>Bind to Platform - Difficult or impossible to dynamically port or migrate. - Little or no use of standards. - Typically older platforms mixed with cloud platforms. - Little use of abstraction. Public Cloud Data Data Private Cloud Internet Data Data Services/API
  53. 54. Assisted Replication - Code port and/or interface compatibility. - Some use of standards. - Typically new platforms that are code/service compatible. - Limited use of abstraction. Public Cloud Data Data Private Cloud Internet Data Data Services/API
  54. 55. Auto Migration <ul><li></li></ul>- Auto code/VM migration and/or interface compatibility. - Some use of standards. - Virtualization, code, and data levels. - Some use of abstraction. Public Cloud Data Data Private Cloud Internet Data Data Services/API
  55. 56. Dynamic Migration Public Cloud Data Data Private Cloud Internet Data Data Services/API - Dynamic VM migration within single logical OS. - Logical and physical abstraction. - Some use of standards. - Hybrid cloud operating systems. OS
  56. 57. Runtime Governance Repository Logs Policies Policies Monitoring
  57. 58. We Need Cloud Abstraction! Private Cloud B Public Cloud C Private Cloud A Common Interface Cloud Management
  58. 59. Define Information <ul><li></li></ul>Data Data Core Physical and Logical Models
  59. 60. <ul><li></li></ul>
  60. 61. Define Services <ul><li></li></ul>Services Data Data Core Physical and Logical Models Core Services
  61. 63. Define Processes <ul><li></li></ul>Services Data Data Core Physical and Logical Models Core Services Core Processes
  62. 64. Map to the Proper Architecture <ul><li>Static Placement </li></ul><ul><li>Assisted Replication </li></ul><ul><li>Auto Migration </li></ul><ul><li>Dynamic Migration </li></ul><ul><li></li></ul>Services Data Data
  63. 65. Select Technology Solution <ul><li>Static Placement </li></ul><ul><li>Assisted Replication </li></ul><ul><li>Auto Migration </li></ul><ul><li>Dynamic Migration </li></ul><ul><li></li></ul>

×