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.

Redefining cloud computing again linthicum with bonus

1,416 views

Published on

In this session we’ll look at what cloud computing is, and what it should be. The way it’s defined today, and how should be defined tomorrow. We’ll focus on the emerging patterns of cloud computing, including changing business value and new patterns of cloud computing technology that are emerging.

Published in: Technology, Business
  • Be the first to comment

Redefining cloud computing again linthicum with bonus

  1. 1. David S. Linthicum David@bluemountainlabs.com Twitter: @DavidLinthicumRedefining Cloud Computing…Again
  2. 2. Abstract: In this session we’ll look at what cloud computing is, and what it should be. The way it’s defined today, and how should be defined tomorrow. We’ll focus on the emergingpatterns of cloud computing, including changing business value and new patterns of cloud computing technology that are emerging.
  3. 3. Where To Find Out MoreSlides available:Bonus Content: Cloud architecture best practices.
  4. 4. Where to find me.• @DavidLinthicum• david@bluemountainlabs.com• www.bluemountainlabs.com• www.davidlinthicum.com• http://www.linkedin.com/in/davidlinthicum• Grab a card after the presentation.
  5. 5. Geek Level for this PresentationYour Grandparents that Systems Programmer andare Still Using AOL Dialup Dungeon Master
  6. 6. The Problem• Current ways of looking at cloud computing are too broad and too limiting at the same time. – No good categorization of sub-patterns. – No definition around where things are going, more so than where they have been.
  7. 7. Why I’m speaking out… • There seems to be an increasing overuse of cloud computing concepts as saviors for all past IT mistakes. • Pushing cloud computing as the way to solve all, or even most, computing problems reveals those who make such statements as less than credible.
  8. 8. So, what is cloud computing? Architecture? Technology? Use cases? What will it be soon?
  9. 9. What is the future?
  10. 10. Datacenters Emerge1940 1950 Rise of Timesharing 1960 Distributed 1970 Computing Grids 1980 1990 Rise of the PC 2000 Rise of Client/Server Rise of the Web 2010 Rise of “The Cloud”
  11. 11. Hardware/Software/Infrastructure On-Demand2010 2012 IT On-Demand Rise of “Big Data” 2014 Rise ofRise of “IT In-a-Box”“Home 2016Clouds” Distributed Rise of Service Sharing “Commodity 2018 Data Services” The “Big 2020 Migration” Begins Rise of Shared Enterprise Business 2022 Services 2024
  12. 12. Cloud Computing is Becoming Systemic
  13. 13. • Buzzword “cloud computing” is absorbed into computing.• Focus on fit and function, and not the hype.• Security moves to “centralized trust” models.• Centralized data becomes a key strategic advantage.• Mobile devices become more powerful, but thin.• The rise of the “composite cloud.”
  14. 14. • Focus on the reorganization and outplacement of data.• Focus on PaaS, and service companies that are good at PaaS.• Focus on centralized trust, including moving to identity management models.• SOA patterns and technology find new value in the cloud.• Continued focus on mobile computing.• Home clouds (e.g., iCloud) create a new track of application and appliance development.• Rise of the “cloud aggregator.”
  15. 15. From here to there…
  16. 16. NIST defines cloud computing as a set of characteristics, deliverymodels, and deployment models 5 Characteristics On-demand self-service Ubiquitous network access 3 Delivery Models  Software as a Service (SaaS) Resource pooling  Platform as a Service (PaaS) 4 Deployment Models Rapid elasticity  Private Cloud  Infrastructure as a Service Pay per use (IaaS)  Community Cloud  Public Cloud  Hybrid Cloud
  17. 17. Delivery Models/Technology Morphing• Software as a Service (SaaS) – Applications as a Service – Utilities as a Service – Connected and Disconnected• Platform as a Service (PaaS) – Design as a Service – Process as a Service – Testing as a Service• Infrastructure as a Service (IaaS) – Database as a Service – Management as a Service – Middleware as a Service – Integration as a Service – Information as a Service …and more.
  18. 18. New Technology Stack Emerging Testing-as-a-Service Management/Governance-as-a-Service Integration-as-a-Service Application-as-a-ServiceSecurity-as-a-Service Process-as-a-Service Platform-as-a-Service Information-as-a-Service Database-as-a-Service Storage-as-a-Service Infrastructure-as-a-Service
  19. 19. Understanding the Emerging Patterns of Architecture Hybrid Private Public CommunitySOA Shared Services Shared Services Shared ServicesSecurity Private Trust Central Trust Tiered TrustData Central Distributed TieredProvisioning Self Self/Auto ManagedTenancy Multi/Distributed Multi Managed
  20. 20. Reference ArchitectureData Services/AbstractionData
  21. 21. Reference ArchitectureTransactional ServicesData Services/AbstractionData
  22. 22. Reference ArchitectureProcess Management Rules Management Composites/Portals(BPMS)Transactional ServicesData Services/AbstractionData
  23. 23. Management & Service GovernanceSecurity & Identity Reference Architecture Monitoring and Management Process Management Rules Management Composites/Portals (BPMS) Transactional Services Data Services/Abstraction Data
  24. 24. 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
  25. 25. So, It’s Something Like This Cloud Computing Public, Private, Hybrid ApplicationApplications Infrastructure Database Security Development Visual (UI Based) Storage Compute Network Management Structured Encryption Identity Design Programming Testing Deployment Middleware Non-Visual Block Self Provisioning Unstructured In Flight UI Code Control Component Provisioning (Services) Object Auto Provisioning At Rest Program Flow Revision Mgmt. Regression Management Process
  26. 26. So, what is cloud computing?• The concept of cloud computing is about the ability for organizations to stop solving all IT problems by themselves.• Cloud computing certainly about sharing resources, such as storage and compute services, but it really should be more about sharing solutions and pushing risk out of the business. – Unfortunately, the focus today is on the tactical side of sharing computing resources. – Should be more about the impact to a business rather than how the technology is defined.
  27. 27. Q&A
  28. 28. The shift to CloudWe are leading the conversationwith thought leadership andcutting edge services.#1 #1 #1BEST SELLING MOST READ MOST LISTENED TO PODCASTBOOK ON BLOG ON ON CLOUD COMPUTING WITHCLOUD COMPUTING CLOUD COMPUTING OVER 10,000 LISTENERS
  29. 29. How to Get Cloud Architecture and Design Right the First TimeDavid S. LinthicumBlue Mountain Labsdavid@bluemountainlabs.com
  30. 30. AbstractSo, what are the proper ways to design, build, and leverage cloudcomputing systems? What are the steps to success? What are theemerging best practices? How does SOA fit in? In this session we’llanswer these questions, and more, covering the right and wrong waysto leverage, design, and build cloud-based systems and infrastructure.Going beyond the hype, this includes advice from those currently in thetrenches who make cloud computing work for the Global 2000 andgovernment. The audience is anyone who will soon fight to make cloudcomputing work for their clients, employers, and/or investors, and needto knock it out of the park the first time.
  31. 31. Where To Find Out MoreSlides available:Bonus Content: How to architect a hybrid cloud computing solution.
  32. 32. Where to find me.• @DavidLinthicum• david@bluemountainlabs.com• www.bluemountainlabs.com• www.davidlinthicum.com• http://www.linkedin.com/in/davidlinthicum• Grab a card after the presentation.
  33. 33. Geek Level for this PresentationYour Grandparents that Systems Programmer andare Still Using AOL Dialup Dungeon Master
  34. 34. Why You Should Care
  35. 35. Most Cloud-Based Systems are Lacking Architecture
  36. 36. 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.
  37. 37. 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.
  38. 38. 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.a software application is “With a multitenant architecture, designed to virtually partition its data and configuration so that each client organization works with a customized virtual application instance.” Source: Wikipedia
  39. 39. The ABCsMultitenancy Source: Lori MacVittie
  40. 40. ABCs of MultitenancyAmazon Machine Images Source: Steve Bobrowski
  41. 41. Virtualization is Not Always a Requirement
  42. 42. Types of Cloud Architecture• Migration Patterns Emerging to a Cloud – Business Systems – Infrastructure Complexity• Building on a Cloud (PaaS)• Building a Hybrid Cloud• Building a Cloud – IaaS – SaaS – PaaS
  43. 43. General Architecture Patterns to Follow
  44. 44. Enterprise Vulnerabilities Assess your Risks1. Governance2. Regulatory Compliance RISK TO ORGANIZATION3. Security & Identity Management4. Business Continuity 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 Assess your vulnerabilities and mitigate your risks.
  45. 45. 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
  46. 46. “as-is”
  47. 47. “to be”
  48. 48. deploy
  49. 49. 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.
  50. 50. Use Case: General Business SystemMigration to the Cloud
  51. 51. 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.
  52. 52. 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.
  53. 53. Management & Service GovernanceSecurity & Identity Reference Architecture Monitoring and Management Process Management Rules Management Composites/Portals (BPMS) Transactional Services Data Services/Abstraction Data
  54. 54. Create the Information ModelLegacy OntologiesMetadata Understand Ontologies Data DictionaryExternal &Metadata Understand the Data Metadata(B2B) Data Catalog Catalog the Data Information Model Build Information Model
  55. 55. Reference ArchitectureData Services/AbstractionData
  56. 56. Create a Service ModelData CandidateCatalog Services Understand Services Services AndInformation InformationModel Information to Services Service Model Build Service Model
  57. 57. Reference ArchitectureTransactional ServicesData Services/AbstractionData
  58. 58. On Premises Cloud Provider
  59. 59. On Premises Cloud Provider
  60. 60. Create a Process ModelData CandidateCatalog Processes Understand Processes Services to ProcessesInformationModel Services to Processes Process ModelService Build Process ModelModel
  61. 61. Reference ArchitectureProcess Management Rules Management Composites/Portals(BPMS)Transactional ServicesData Services/AbstractionData
  62. 62. On Premises Cloud Provider
  63. 63. Create a Governance ModelProcess DefinedModel Policies Define Policies Policy DesignsInformationModel Design Policies Governance ModelService Implement PoliciesModel
  64. 64. Management & Service GovernanceSecurity & Identity Reference Architecture Monitoring and Management Process Management Rules Management Composites/Portals (BPMS) Transactional Services Data Services/Abstraction Data
  65. 65. Policies PoliciesRuntimeGovernance Monitorin gRepository Logs
  66. 66. Test SOA using Cloud ArchitectureProcess TestModel Plan Create Test Plan Black Box TestingInformation ResultsModel Black Box Testing White Box Testing ResultsService White Box TestingModelGovernanceModel
  67. 67. Assigning Candidate Data, Services, and Processes for the Clouds ProcessCandidate AssignmentsProcesses Analyze Candidate Processes Service AssignmentsCandidateServices Analyze Candidate Services Data AssignmentsData Analyze Candidate DataDictionaryandMetadataGovernanceModel
  68. 68. Select Platforms and Deploy Processes, Services, and Data to Platforms. Candidate PlatformsProcess List Candidate PlatformsAssignments Test ResultsServiceAssignments Analyze and Test Candidate Platforms Target PlatformsDataAssignments Select Target Platforms Deploy to Target Platforms
  69. 69. Data Services ProcessesDataDataDataData
  70. 70. Data Services Processes Data PaaS Data Data DataDaaS IaaS
  71. 71. Data Services ProcessesApplication Data PaaS Data Application Data DaaS Data IaaS
  72. 72. Stepping to the Clouds1. Access the mission. 11. Create a governance strategy.2. Access the culture. 12. Create a security strategy.3. Access the value. 13. Bind candidate services to data4. Understand your data. and processes.5. Understand your services. 14. Relocate services, processes,6. Understand your processes. and information.7. Understand the cloud 15. Implement security. resources. 16. Implement governance.8. Identify candidate data. 17. Implement operations.9. Identify candidate services10. Identify candidate processes.
  73. 73. Q&A
  74. 74. The shift to CloudWe are leading the conversationwith thought leadership andcutting edge services.#1 #1 #1BEST SELLING MOST READ MOST LISTENED TO PODCASTBOOK ON BLOG ON ON CLOUD COMPUTING WITHCLOUD COMPUTING CLOUD COMPUTING OVER 10,000 LISTENERS
  75. 75. Additional Slides
  76. 76. Use Case: Creating an Hybrid Cloud
  77. 77. Current Patterns: Primitive Hybrid Architectures Migration Public Private Cloud Cloud Interoperability Public Private Cloud Cloud API/Services
  78. 78. Best: Cloud Abstraction Public Cloud C Abstraction Private Layer Cloud B (Composit e) Private Cloud A
  79. 79. Emerging Hybrid Cloud Architectural Patterns• Static Placement• Assisted Replication• Auto Migration• Dynamic Migration 82
  80. 80. Static Placement Data Data - Difficult or impossible to dynamically port or migrate. - Little or no use of standards. - Typically older platforms Private Cloud mixed with cloud platforms. - Little use of abstraction.Bind to Services/APIPlatform Public Cloud Data Data 83
  81. 81. Assisted Replication Data Data - Code port and/or interface compatibility. - Some use of standards. - Typically new platforms thatPrivate Cloud are code/service compatible. - Limited use of abstraction. Services/APIPublic Cloud Data Data 84
  82. 82. Auto Migration Data Data - Auto code/VM migration and/or interface compatibility. - Some use of standards. - Virtualization, code, andPrivate Cloud data levels. - Some use of abstraction. Services/APIPublic CloudData Data 85
  83. 83. Dynamic Migration Data Data - Dynamic VM migrationOS within single logical OS. - Logical and physical abstraction. Private Cloud - Some use of standards. - Hybrid cloud operating systems. Services/API Public Cloud Data Data 86
  84. 84. Policies PoliciesRuntimeGovernance Monitorin gRepository Logs
  85. 85. We Need Cloud Abstraction! Public Cloud C Private Common Cloud B Interface Cloud Management Private Cloud A
  86. 86. Define Information Data DataCore Physical and Logical Models 89
  87. 87. 90
  88. 88. Define Services Services Core Services Data DataCore Physical and Logical Models 91
  89. 89. Define Processes Core Processes Services Core Services Data DataCore Physical and Logical Models 93
  90. 90. Map to the Proper Architecture • Static Placement • Assisted ReplicationServices • Auto Migration • Dynamic MigrationData Data 94
  91. 91. Select Technology Solution• Static Placement• Assisted Replication• Auto Migration• Dynamic Migration 95

×