platform as a service overview
TRANSCRIPT
PaaS: a simple overview
Miguel Angel Pastor Olivarmiguelinlas3 at gmail dot com
http://miguelinlas3.blogspot.comhttp://twitter.com/miguelinlas3
Contents
Introduction
An abstract model
Differential aspects
Taxonomy
A real vision
Contents
Recommendations
A real example
Introduction
Introducción
Cloud computing hottest word in IT
Available PaaS types?
New procedures and practices?
Wide range of business solutions?
Support to legacy code?
An abstract model
Abstract model
Provides all time features
Adding new features
Wide range of languages and platforms
Hard support to legacy code
Runtime in vendor´s datacenter
Main admin task: user management
Diferential aspects
Main diferential aspects
Development
Runtime
Management
Administration
More diferential aspects
Not current platforms hosted by thirds
Rewriting code
Application patterns
Reduced control
Statless states and petabytes apps
Sharing info over Internet (no transactions)
Index, search, categorization over high volume of dynamic data
More diferential aspects
Division of responsibilities
Vendors take on reliability
No fine grained control
Automatic scaling and multi-tenant
Vendors responsibility
New subscription model
Pay as you go
No all vendors provide billing mechanism
More diferential aspects
Tailored tools and life-cycles
Extensibility
Partnership mechanisms
Reliability based on multiple vendors
Lock-in vendor
Serious problem
Taxonomy
Taxonomy
3GL and content oriented applications
3GL and transactional applications
4GL and content oriented applications
4GL and transactional oriented applications
Business developers and content applications
Business developers and transactional apps
A real approachGoogle App Engine
(GAE)
GAE: main features
Dynamic web services
Popular web frameworks
Persistent storage
Querying, sorting and transactions
Automatic scaling and load balancing
Authentication API and email sending
GAE: main features
Local development environment
Task queues
Perform work outside web request´s scope
Task planning
GAE: sandbox
Secured environment
Restringed access to operating system
Http(s) connections available
Drawbacks
Access to other apps: mail and url fetching
No writing disk is available
Code excution on web requests (30 seconds)
GAE: storage
Elastic, querying, transactional storage service
No relational database
Hard consistent model
Optimistic concurrent control
GAE: google accounts
Google accounts integration
Proven management module system
Not necessary writing our own module
GAE: other services
Services to application management
URL Fetch
Emailing
Memcache
Image manipulation
GAE: Limits and quotas
Free accounts
Storage: 500 Mb
5 millions visits/month
10 different apps on each account
Limits exceeding
Pay as you go
Another vision:VMForce
VMForce: intro
Business platform as a service
Based on proven and popular technologies
Relational databases
Spring framework
VMWare virtualization
force.com infrastructure
VMForce: problems
Business apps mucho more than database and application server:
Searching
Reporting
Movility
Integration
Business process
User management
Application management
VMForce: problems
Business apps mucho more than database and application server:
Searching
Reporting
Movility
Integration
Business process
User management
Application management
VMForce: build
IDE Based (Spring Tool Suite)
Java code
Data in force.com
Drag and Drop
VMForce: execution
VMWare vSphere
Vcloud
tcServer
VMForce: management
Not too much management
Application logic is our main focus
Recommendations
Recommendations
Identify content oriented applications
Hard work loads to move
Other work loads to move
Economic benefits evaluation
Risk evaluation
Lock-in vendor
SLA evaluation
Lifecycle evaluation
Conclusions
Conclusions
Becoming a reallity
Popular technology at incoming years
Problems to solve
Vendor locking
Programming models
Interesting area
That´s all!!Thank you!