linthicum next generation-iaa s-paas-and-database-as-a-service

© 2013 Cloud Technology Partners, Inc. / www.cloudtp.com

1

[email protected] / Senior Vice President / May 6, 2013

Next Generation IaaS, PaaS &Database as a Service


2

Understanding the Emerging Patterns of Architecture

High Growth Expected in Cloud Infrastructure Services


3


4

IaaS


5

Gartner recently reported that IaaS continues to be the fastest growing of the current cloud services. In 2012 it grew 42.4 percent to $6.1 billion and has an expected growth of 47.3 percent in 2013 to $9 billion.

IaaS is Growing Fast


6

External Service Providers Being Considered for IaaS (or Cloud IaaS)


7

The Most Popular IaaS


8

AWS


9

CloudStack


10

OpenStack


11

Database-as-a-Service


12

Service-Enabled Database Access Methods


13


14

Cloud Database Vendors by Deployment & Data Model


15

PaaS


16

• Good– Budget - It’s cheap.

– Power - It scales.

– Development – It’s productive.

• Bad– Limitations - Can only use what’s there.

– Standards - Few exist.

PaaS in the Real World


17

Major PaaS Players

Most Popular

Most Misunderstood

New Guy


18

• Sandbox approach (top down)

• Highly limited

• Simplicity tradeoff at expense of developer control

Google App Engine


19

Heroku

Routing Mesh

Dyno Grid

SQL Database

Memory Cache

• Sandbox approach (top down)

• Highly limited

• Simplicity tradeoff at expense of developer control


20

Elastic BeanstalkApplication

• Bottom-up approach

• Simplicity with a higher degree of control for the developer

Elastic Beanstalk

AutoScaling

http://myapp-staging.elasticbeanstalk.com/

Elastic Load Balancer

Apache

Tomcat

Amazon Linux AMI

Your Running Application

EC2 Instances

EC2 Instances

EC2 Instances

VersionVersion

VersionEnvironment

Elas

tic B

eans

talk

Hos

t Man

ager


21

• Make sure to consider the target application.– Static application requirements often lead to PaaS not being a fit.

• Make sure to consider resources required.– PaaS clouds limit use of resources, or they become too expensive quickly.

• Make sure to consider data persistence.– Data support varies greatly.

• Make sure not to get religious around the languages.– “We’ll do it in any language as long as it’s Python.”

• Make sure to consider leveraging the outside world. – Need to interact with other clouds, and on-premise systems.

• Make sure to consider staging and testing.

Real World Advice


22

• Start with the data, and work up to the services and UI. Not matter what the PaaS provider suggests.

• Create an initial POC, and make sure to validate the complete stack.

• Define a staging and testing strategy before you begin development.

• Consider SOA approaches in the design and deployment of the PaaS-based application.

• Make sure to do load testing along with functional testing.

• Make sure to model performance.

• Don’t fall in love with a PaaS player. You may need to use several.

Best Practices


23

PaaS Attributes


24

Vector: Application Development• Company: Google

• Company: Salesforce.com

• Company: Engine Yard

Vector: Application Infrastructure• Company: Amazon

• Company: Google

• Company: Microsoft

Vector: Database Management• Company: Amazon

• Company: Google

• Company: Microsoft

PaaS Provider Ranking


25

Relative Importance of PaaS Platform Disruption Vectors


26

PaaS Platform Vendors Scored Against Disruption Vectors


27

Ask by email / [email protected] / www.cloudtp.com

Questions?