PaaS. The Promise of. Dr. Donald F. Ferguson Sr. Fellow, VP, and Chief Technology Officer Dell Software Group

Transcription

1 The Promise of Dr. Donald F. Ferguson Sr. Fellow, VP, and Chief Technology Officer Dell Software Group Dr. Craig Lowery Sr. Distinguished Engineer & Director of Cloud Architecture Dell Software Group

2 WHAT IS IT? It has many meanings and is ambiguous in many aspects Soup to nuts lifecycle for software (design, dev, distro, deploy, operate, update, retire)? Middleware that closes the gap between infrastructure and software developers? A technology stack, or a proprietary service, or sometimes both? Language specific? Language independent? Infrastructure specific? Infrastructure independent? Things we can say for certain CONFUSED? (don t feel bad ) It is closer to the application and the developer than IaaS It relieves developers of having to re-implement commonly needed software patterns It will soon eclipse IaaS in importance for deriving the full potential of the cloud 2

3 Number of Instances in the World Hypothesis: Trajectory of Computing Utility Models Physical App Hosting SaaS is applications it will always top the mix as applications shift to the model There is a coming inflection point where apps are written to a instead of traditional OS/infrastructure stacks 3 DELL Software as a Service Platform as a Service ( Hosting) OS Virtual Machines (IaaS) We are here? 2020? ? 2020?

4 Mgmt. and Security Gartner s Study (Real Data) df 1. How have companies successfully used cloud system infrastructure services, and what lessons can be learned? 2. How have companies successfully used cloud application infrastructure services and what lessons can be learned? 3. How have companies successfully used cloud application services and what lessons can be learned? Infrastructure Services Business Services Information Services Services App. Infrastructure Services Cloud Enablers 4

5 is a Spectrum Subscription Access Presentation Billing Business domain solutions SaaS More hardware-bound Traditional App on general OS Local resource dependent Fewer programming constraints Traditional App on a Physical Machine Traditional App on a Virtual Machine Service Oriented App in a Container More virtualized, service oriented Prescriptive programming model Faster app development Automatic scalability Service Oriented App on a Distributed Compute Storage Network IaaS 5

6 Review of Cloud Delivery Models (a.k.a. Everything is SaaS after all is said and done) 6

7 What is? NIST Cloud Computing Reference Architecture The NIST RA attempts to make formal sense of the delivery models, but the reality isn t nearly this clean. 7

8 Understanding IaaS Workloads Workloads targeting the IaaS layer are traditional virtual machines containing a legacy OS (Windows, Linux) and an application. Deploying an IaaS workload requires: Creating the Creating the image (virtual hard disk) by traditional installation or cloning Finding or adding capacity in the infrastructure to deploy Placing and starting the The least efficient way to put applications into the cloud IaaS Data Center 8

9 Understanding Workloads Workloads targeting the layer are bundles of application code (Java,.NET). The platform, typically s cooperatively executing a runtime, is already deployed creating the layer. Deploying a workload requires: Importing the bundle into the environment Determining if there is capacity to run it, and adding more if needed Starting the application Provides an environment for writing/running general purpose software without being business-domain specific App App App App App Environment App App App IaaS Data Center 9 9

10 Understanding SaaS Workloads SaaS (Software as a Service) workloads are actually new users The application is already deployed and running Deploying a SaaS workload requires: Determining if capacity exists for another user, and increasing if needed Adding the user to the user access database for the application SaaS is building out the business-domain specific logic (the application) and making it available as as service. Environment IaaS Data Center 10

11 Mixing Layers and Location It is possible to have workloads deployed at all three layers, perhaps even in multiple clouds. Connecting and managing the components that make up an app is a hard problem! Environment App App App App App App App App Environment IaaSData Center SalesForce.com IaaSData Center Windows Azure IaaSData Center Amazon Web Services App App App 11

12 IaaS and Example Services Comparison Typical Services Typical IaaS Services Process/threading model Database (SQL, nosql) Messaging (queues, buses) Software modularity (IoC frameworks) Presentation layer offload (UI frameworks) Role-based program feature access URI-based communication.many more Compute (virtual machine) Storage (block, file) Network (IP, VLAN) Load balancer DNS mapping Security (authentication, access) services are built on IaaS services, but are more easily consumed by a software developer because they map directly to common programming constructs, such as data structures and software architecture patterns. 12

13 SaaS doesn t compete with IaaS or Paas.it is the purpose of them! An IaaS is a comprising low-level service abstractions but in general, means abstractions to help software devs. is potentially an easier/faster/cheaper way to create applications, usually delivered as a SaaS. 13

14 Is The Next Wave (and it s already rolling onto the beach) 14

15 and SaaS: It s all about the apps! Why conventional s will be phased out: Users want to have hosted and access to applications and associated data, not an OS OS s are just a quick and dirty way to virtualize legacy applications (avoid rewrite/redesign) OS s are too large to efficiently migrate within the cloud Reusable implies portable - object framework technologies, containers, and development environments make it possible to reliably create portable objects and applications The focus is shifting from OS s to application hosting as a service () Microsoft Azure is a prime example.net in the cloud Many other examples exist in open source (OpenShift, CloudFoundry) Containers are taking center stage (Docker) Over time, apps will be re-written to take advantage of The efficiencies of the application hosting and container model The flexibility of an elastic infrastructure (adjusts to demand, availability and resiliency in the software layer) The faster time to delivery of applications (weeks, not months) thus increasing business velocity 15

16 Composite s Argue for Multiple Technologies Microsoft SAP SCA LAMP Force.com J2EE Spring Composite apps are well suited to. Each component could potentially leverage a different (most appropriate) platform. One will not likely fit all. 16

17 Cloud Spanning Apps Imply Hierarchical We need platforms to host each component. order history And a platform that can bind them together across the Internet into a functioning app. UI portal workflow process If Approved then Send letter offering gold If NOT Approved Send letter offering Credit counseling service get Approved Approved/ Denied logistics application contact management credit check BSaaS API 17

18 Key Things To Remember isn t coming, it s already here. You need to understand how this change impacts your business. IaaS is at bottom of the cloud abstraction layer it s all (a spectrum) Cloud services will continue to become more abstract as they go right The limit on the right is Business Services everything is gravitating toward that The value is real it enables you to get applications built and deployed faster In the IaaS phase, it is relatively easy to swap out services could lock you in It is important to continue to enable customer choice (interoperability and portability) Standards are one way to do that, but what role standards play (if any) is not clear We re here today to discuss how the industry can best serve customers as they move further right on the spectrum. 18

19 Thank you