24
© 2013 Cloud Technology Partners, Inc. / Confidential 1 The Many Faces of PaaS Platform as a Service Decisions Mike Kavis 10/08/2013

The Many Faces of PaaS

Embed Size (px)

DESCRIPTION

By now, enterprises understand the value of Software as a Service (SaaS) and Infrastructure as a Service (IaaS), but there still is much confusion about Platform as a Service (PaaS). This confusion is one reason why enterprises have been slow to adopt PaaS. Why is there so much confusion? This presentation will help clear up the confusion of all the different types of PaaS offerings in the marketplace.

Citation preview

Page 1: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

1

The Many Faces of PaaS

Platform as a Service Decisions

Mike Kavis

10/08/2013

Page 2: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

2

About the Presenter

@madgreek65

mikekavis

madgreek65

VP/Principal Architect @ Cloud Technology Partners

Mike Kavis

Agile Development

madgreek65

Page 3: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

3

• Cloud Service Models

• Evolution of PaaS

• PaaS in 2013

• Conclusion

Agenda

Page 4: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

4

Cloud Service Models

Page 5: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

5

The Cloud Stack

Page 6: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

6

Infrastructure as a Service

Page 7: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

7

Platform as a Service

Page 8: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

8

Software as a Service

Page 9: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

9

Pros Cons

Speed to Market Less Control

PaaS handles autoscaling, fail over, disaster recovery Only suitable for certain workloads, not high transactions

PaaS manages many security requirements Little to no input into security controls and audits

PaaS manages software updates, patches No input or insights into vulnerabilities

PaaS manages uptime, reliability Most have no published SLAs and can’t meet SLAs beyond 4 9’s

Integrated with numerous third party software vendors Might not integrate with the vendors in your enterprise

Cost effective method of utilizing compute resources Costs can spiral out of control if not governed properly

Most likely the preferred method of development in the near future

Immature and unproven in current day and age

Pros and Cons of PaaS

Page 10: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

10

Evolution of PaaS

Page 11: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

11

Characteristics Description

Abstracted infrastructure The entire infrastructure layer is the responsibility of the PaaS vendor enabling developers to focus on business requirements and not the underlying plumbing (patching, installing, scaling, failover, etc.)

Managed App Stack The application stack can be deployed with a few clicks of a mouse

Pay as you go Only pay for the services you use

Integrated tools Numerous third party “plugins” (ex: Redis, SendGrid, Loggly, New Relic, RabbitMQ, etc.)

Speed to market Quickly stand up environment to build apps

Throttling Governors in place to protect against tenants flooding the system

Language challenged APIs support a single application development language and possibly even a proprietary language

Lock in Developers locked into the platform, challenging to move off

Public PaaS – Single Stack

Page 12: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

12

Characteristics Description

Abstracted Infrastructure The entire infrastructure layer is the responsibility of the PaaS vendor enabling developers to focus on business requirements and not the underlying plumbing (patching, installing, scaling, failover, etc.)

Managed App Stack The application stack can be deployed with a few clicks of a mouse

Pay as you go Only pay for the services you use

Integrated tools Numerous third party “plugins” (ex: Redis, SendGrid, Loggly, New Relic, RabbitMQ, etc.)

Speed to market Quickly stand up environment to build apps

Throttling Governors in place to protect against tenants flooding the system

Language enabled APIs offer support for numerous application stacks (ex: Ruby, Python, PHP, Java, .Net, Node.js, etc)

Lock in Developers locked into the platform, challenging to move off

Public PaaS – Multi Stack

Page 13: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

13

Characteristics Description

Infrastructure not abstracted

The PaaS is a software application that must be implemented and managed on top of infrastructure which is not abstracted.

Managed App Stack The application stack can be deployed with a few clicks of a mouse

Pay for everything Classical IT payment model. Pay for hardware, software, services, etc.

Integrated tools Numerous third party “plugins” (ex: Redis, SendGrid, Loggly, New Relic, RabbitMQ, etc.)

Speed to market eventually

Still quick for developers but lots of the same old work for systems admins plus the additional responsibility of managing the PaaS software

Throttling Governors in place to protect against tenants flooding the system, but admins can add infrastructure as needed

Language enabled APIs offer support for numerous application stacks (ex: Ruby, Python, PHP, Java, .Net, Node.js, etc)

Less lock in With open source version of PaaS, much less lock in

Private PaaS – Multi Stack

Page 14: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

14

• Public Hosted– Classic PaaS model; Vendor runs PaaS on its own infrastructure in a public cloud

• Public Managed– Vendor runs PaaS on an IaaS vendor’s public cloud and manages the PaaS on your behalf

• Public Unmanaged– Vendor runs PaaS on an IaaS vendor’s public cloud and you managed it

• Private Hosted– Vendor runs PaaS on its own infrastructure in a private cloud

• Private Managed– PaaS solution is software only installed on a private cloud, vendor manages the platform on

your behalf

• Private Unmanaged– PaaS solution is software only that you install and manage yourself in a private cloud

Types of PaaS

Page 15: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

15

How the different PaaS options stack up

Page 16: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

16

How the different PaaS options stack up

Page 17: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

17

PaaS in 2013

Page 18: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

18

• Enterprises cloud adoption is not a binary decision

• Enterprises will deploy multi cloud solutions– Iaas, PaaS, and SaaS clouds

– Public, Private, Hybrid, and Community clouds

• Enterprises will pick the different tools for different jobs

• Cloud silos will emerge just like application silos have for years

Multi Cloud Realities

Page 19: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

19

• More focus needed on security and governance to deal with complexity

• Many moving parts makes resiliency a challenge

• Multi clouds have value if you select the right providers for the right use cases

• Cloud management platforms are critical for managing the complexity

• “Don’t try this at home”– Leverage cloud experts like CloudTP who have years of experience dealing with complex

cloud implementations

– Requires deep understanding of application, infrastructure, and enterprise architecture

– Requires deep knowledge of cloud vendor offerings across a wide range of services

Multi Cloud Implications

Page 20: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

20

• Public– Speed to market

– Outsource management of infrastructure when possible

• Private– Data security and privacy (PII data, PCI, HIPAA, etc.)

– Legacy systems (mainframes, stateful applications, etc.)

– High transactional and low latency systems

• Bare Metal– Workloads on bare metal machines

– Specific hardware requirements for certain apps

Enterprise Requirements

Page 21: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

21

Domain Specific PaaS Solutions Emerging

DevOps

Mobile Social

Big Data

Page 22: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

22

Conclusion

Page 23: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

23

Choosing the right PaaS for the right reasons

• Use the right tool for the right job

• Leverage cloud experts where applicable

• Understand which workloads/apps make sense to build with PaaS– Understand Regulatory & Compliance requirements

– Capex vs. Opex

– Time to market considerations

• Other factors– Organizational maturity, readiness

– Customer/industry perception of cloud

Page 24: The Many Faces of PaaS

© 2013 Cloud Technology Partners, Inc. / Confidential

24

Questions?