2014 brings more maturity and alternatives than ever when it comes to providers of Cloud Computing services and software. With this increasing maturity, the variety of viable usage scenarios for cloud computing is exploding as well. However, all this variety can make it harder to choose the right direction, given your use case.
Mick Bass will provide an Overview of the “State of the Union” of Cloud Computing service and software providers, as well as common business and technology scenarios that drive adoption of Cloud Computing. We’ll cover public, private, hybrid, infrastructure-as-a-service, platform-as-a-service, automation, security, and key economic differences that come into play when deciding on the right alternative for you - and we’ll be sure to leave ample time for a fun and vibrant Q&A and discussion. Mick is CEO of 47Lining, a Boulder–based consultancy that provides Cloud Advisory and Development Services to enterprise customers, focused on the creation of cloud-native data platforms.
Presented at Front Range PHP Users Group, May 21 2014
Scaling API-first – The story of a global engineering organization
47Lining - Cloud Computing State of the Union 2014
1. State of the Union
Cloud Computing Services & Software
2014
@47lining
www.47lining.com
1
2. The Menu
Intro
• About Us
• What Drives Cloud Adoption? For Who? With What First Steps?
The LandScape
• Stack Providers | IT Providers | Distributions
• Iaas | PaaS | SaaS
• Public | Private | Hybrid
• New Entrants & Established Players
• Transformation: What’s Happening Here?
Which Offerings are Right for You?
• “Cloud-Native” Application & Platform Development
• APIs & Automation
• “Feature Complete”ness
• Economics
TakeAways
• Some Suggestions
• Discussion / Q&A 2
3. About Us
• Boutique, highly specialized consultancy
• We help our customers drive new revenue
through Cloud-enabled transformation initiatives.
• Practices:
– Cloud Strategy
– Cloud-Native Software Development
– Cloud Automation & Operations
3
4. The Framing for this Story
Source: Modularity in the Design of Complex Engineering Systems,
Carliss Baldwin and Kim Clark. January, 2004
IBM
electronic
computers
networking
equipment
semiconductors
programming
services
Packaged
software
Microsoft
4
6. Why Cloud Adoption?
Adoption Scenarios
• Dev/Test
• Autoscaling Web / Mobile Apps
• Backup / Disaster Recovery
• Integration / Façade Services
• B2B Data Collaboration Ecosystem
• Data Manufacturing / HPC
• Analytics
• Application Services Migration
Adoption Drivers
• Cost
• Agility / Speed
• CapEx -> OpEx
• Scale / Volatility
Cloud Adopters
Employees | Dev Teams | Startups | Business Owners | IT Owners
6
7. Stacks | Big IT | Distributions
Cloud
Transformation
“Big Stacks”
Distributions“Big IT”
Provide Capital for Physical
Capacity
Productize Large-Scale
Offerings
(Business & Consumer)
Provide Technology Underpinnings
For Cloud Mgmt Platforms
Provide IT Business Solutions and
Transformation Services 7
8. The “Big Stack” Providers
All have different motivations & entry paths to Cloud Services.
(This is important!)8
9. The “Big IT” Providers
Acquisitions
Product and Consulting Services Investments
Forward and Backward Integration
Support for Distributions9
11. Cloud Services “Pyramid”
Transformation
Services
Software
as a
Service
Platform
as a
Service
Infrastructure
as a
Service
Managing Migration to
New IT Paradigms
Business & Consumer
Apps
Application Deployment
Scaling / HA
Monitoring
Compute
Networking
Storage
11
12. Public | Private | Hybrid
Public
MultiTenant
Private
Biz1
Private
Biz2
Private
Biz3
Private
Biz …
12
14. What’s Happening Here?
Business
IT Spend
Traditional
Private
Public
Hybrid
IaaSPaaSSaaS
Market
IT Spend
IaaSPaaSSaaS Traditional
Private
Public
Hybrid
Transformation
“Big IT”
“Big Stacks”
• Investment
• Innovation
• “Product Releases”
14
16. Transforming Enterprise IT
U.S. Top IaaS Provider Preferences;
(Source: IBM – IDC's U.S Outsourced Cloud Services Survey, 4Q13) 16
17. OpenStack Momentum
• Significant investments by
“Big IT Players”; however
• Fragmentation in
Distributions
• Hard to compete with
investment & clockspeed
of “Big Stack” players
• Difficult to build public &
private offerings
simultaneously
17
19. API’s & Automation
• Cloud IaaS APIs enables automation tooling
– Puppet | Chef | Ansible | Salt
• Proprietary “Stack Builders” (e.g. CloudFormation) can also be used to bootstrap
entire environments for further tooling via automation.
• Different Providers currently provide APIs with varying granularity.
• Open-source language-specific SDKs sometimes wrap service-provider APIs (e.g.
boto).
• There is an open-source marketplace for common playbooks / cookbooks using
various providers. Earlier offerings generally have an advantage in this regard.
• Environment “Reflection” capabilities can provide an easy-entry path to
automation from manually constructed environments.
19