© NICTA 2008 Slide 1 of 44 Moderated by: Vladimir Tosic (NICTA) MW4SOC 2010 Discussion Session Middleware for Clouds vs. Middleware for Other SOC: What Is Different and What Is Not?

Example Discussion Points Suggested by the Moderator Some of these points are from: K.M. Göschka, P. Brebner, H. Wada, P. Bannerman

© NICTA 2008 Slide 3 of 14 Some Possible Discussion Points © NICTA 2010 In which ways is cloud computing substantially different (or NOT) from other SOC initiatives? How do these differences (e.g. virtualization) affect (or NOT affect) middleware? Is cloud computing too diverse to speak about distinctive “cloud middleware”? What SOC middleware knowledge/experience can (or can NOT) be reused in cloud systems? What open research issues are specific for cloud middleware (or shared with other SOC middleware)? …

© NICTA 2008 Slide 4 of 14 Cloud Computing: What It Is / Is Not? Within the broad view of SOC (not only Web services) Earlier SOC initiatives similar to cloud computing: utility computing, on-demand-computing, … Also related to: grid computing, virtualization, … Different layers: IaaS (Infrastructure as a Service), PaaS (Platform), SaaS (Software), …. Private, hybrid, community, public clouds Different business models (not only pay-per-use) “Liberal use” of the term “cloud” by marketing © NICTA 2010

© NICTA 2008 Slide 5 of 14 Middleware and Cloud Diversity Grid middleware + virtualization ~> IaaS Distributed operating systems ~> PaaS Web services middleware ~> SaaS Middleware for private clouds vs. data centers Challenges in hybrid and community clouds “Inter-cloud” middleware What is the impact of different business models on middleware? © NICTA 2010

© NICTA 2008 Slide 6 of 14 Middleware and Cloud Elasticity Middleware for achieving elasticity and for dealing with side-effects of elasticity The need for adapting to various changes o Past work on middleware for SOC adaptation Quality of service (QoS) guarantees of/using clouds o Past work on QoS middleware for SOC Management when there is no full control over clouds (particularly non-private) o Orientation towards shared remote management © NICTA 2010

Some Insights and Opinions from the MW4SOC 2010 Workshop Participants Systematized short excerpts from the discussion notes kept by U. Bellur

© NICTA 2008 Slide 8 of 14 The Cloud Computing Fuzziness Cloud computing is a popular buzzword nowadays The same (or very similar) concepts as in SOC are marketed in different ways There is a lot of reinventing the wheel Map-reduce is not new – it is several decades old Clouds evolved from grids and added virtualization SOC can leverage clouds (e.g. as middleware) Cloud services are offered as SOC Clouds are “killer apps” for middleware (while SOC provides context) © NICTA 2010

© NICTA 2008 Slide 9 of 14 Cloud Computing vs. SOC (Slide 1 of 2) There are very different opinions about how clouds relate to SOC, depending on used definitions of clouds, SOC, and SOA (the main SOC example) 1. Cloud computing as a subset of “broader-view” SOC o in this view, SOA is another subset of SOC 2. Cloud computing as a generalization of SOC o cloud computing is about providing various resources as services, o not only code execution as SOC (SOA) in this view does © NICTA 2010

© NICTA 2008 Slide 10 of 14 Cloud Computing vs. SOC (Slide 2 of 2) 3. Cloud computing and SOC work on different layers o while SOC (SOA) provides coarse-grained functionality, o clouds (IaaS and PaaS) in this view provide lower- level computing capability 4. Cloud computing and SOC have different goals o while SOC (SOA) is about loose coupling as a paradigm for building applications, o cloud computing is about sharing resources and leveraging a set of resources to its fullest to amortize costs across users © NICTA 2010

© NICTA 2008 Slide 11 of 14 Some Common Important Concerns There are many concerns in cloud computing common with SOC, where past SOC results could/should be leveraged, such as: o Formalization of various types of functional and extra-functional contracts between clouds and o QoS and SLA definition o Service and QoS negotiation o Monitoring o Real-time control o Scalability o Dependability functions © NICTA 2010

© NICTA 2008 Slide 12 of 14 Some Specific Cloud Concerns (Slide 1/2) Virtualization Multi-tenancy is an important requirement for cloud infrastructure (and middleware) o Supports pay-per-use, but complicates other aspects There are additional security and privacy issues Scale is different (often much bigger) in the clouds Interoperability and portability between clouds o There is a need for open cloud standards, but this might not be in the interest of some market players o “ Inter-cloud” middleware would be useful for users © NICTA 2010

© NICTA 2008 Slide 13 of 14 Current speed/latency of Internet is prohibitive for some uses of clouds Monitoring (metering) and control are challenging Need to separate the communications aspects from the container aspects of middleware o The communications aspects of middleware are the same whether you are consuming computational capability vs. consuming software as a service o On the contrary, the containers that manage the server-side components are vastly different for software services vs. computational services © NICTA 2010 Some Specific Cloud Concerns (Slide 2/2)

© NICTA 2008 Slide 14 of 44 From imagination to impact Let’s continue this discussion... (Subject: “MW4SOC 2010 Discussion”)