Develop, Deploy, Scale

Seema Jethani / @seemaj

About the Speaker

• Director of Product Management @enstratus

• Lead Technical Special Interest Group @ Cloud Network of Women

• 10 years of experience in enterprise software development, strategy, product management

Things to consider when evaluating PaaS

solutions

The GOOD and the BAD

The magic that is Platform as a Service

Standardizing middleware infrastructure services

Simplified deployment

Improved productivity

Ability to rapidly test multiple configurations

Easy to manage software upgrades

Bottom Line Faster time to market

Where is the magic?

When evaluating PaaS what factors are most important?

Other factors to consider

Well defined APIs and SDKs

Monitoring, debugging, analytics

Performance

Integration to on-premise data-center

Data Portability

User experience, accessibility

Management and control over development and deployment lifecycle

The Public vs Private Debate Public Private

Time to Value Security and Privacy

Flexibility over Platform Architecture

Compliance

Ease of on-boarding Flexibility over platform and infrastructure components

Security and Privacy Time to Value

Compliance Ease of on-boarding

Top reasons for selecting PUBLIC PaaS

Top reasons for selecting PRIVATE PaaS

The case for build your own

Lack of vendor that meets needs

Ease of on-boarding

Flexibility over infrastructure components

Security, Privacy and Compliance

Flexibility over infrastructure components

Top reasons for selectingBUILD YOUR OWN PaaS

What about that competitive advantage?

• Are you spending far too much money in IT on things that don’t really matter?

• If you are a car manufacturer would you Hire developers that can

build a kick ass PaaS to meet your needs?

Hire developers that can put various existing components together to meet your needs?

Should we care about Open PaaS?

Arguments usually made in favor of Open PaaSMost PaaS providers only provide a serviceThey usually require you to use their proprietary frameworkThere is no-way to leverage the code you created to run apps on another cloud.

Which of these arguments really has merits?

It Depends…

Should we care about Open PaaS?Most PaaS providers only provide a service

May not want to get tied to a vendor that offers limited choices

They usually require you to use their proprietary framework May not want to get tied to a proprietary framework unless business

largely depends on it

There is no-way to leverage the code you created to run apps on another cloud. Vendor lock-in isn't evil

If vendor meets needs, that vendor is a better choice versus an open PaaS provider that may require compromise

THANK YOU!