The Cloud Native Journey

© Copyright 2015 Pivotal. All rights reserved. 1
The Cloud Native Journey
Matt Stine (@mstine)
Principal Engineer & Senior Product Manager

WARNING:
!
This may end up
being a bit stream
of
consciousness…

© Copyright 2015 Pivotal. All rights reserved.
My Cloud Native Journey
3
App Dev/Arch
for 11 years
CLOUD NATIVE LAND

I wrote a little cloud book…
Available to you
compliments of Pivotal and O’Reilly!
!
Book Signing @ 10:00 AM:
North Hall, Hall E (Hang Space)
!
Get the FREE e-book
at http://bit.ly/cloud-native-book!

“Software is Eating the World”

Gartner predicts that by
2020, 75 percent of
application purchases
supporting digital
business will be
"build," not "buy."
http://www.gartner.com/newsroom/id/3119717

The ability to deliver software is no
longer a differentiator.

It is a basic requirement for survival.

So what do the Cloud Natives do?
$3.5B valuation
Financial Services
$3.5B valuation
Travel & Hospitality
$3.5B valuation
Transportation
$3.2B Acquisition by Google
Home Automation
$20B valuation
Entertainment
$26B valuation
Tesla--Automotive
$6B $50B $41B
$25B $33.5B

SPEED
UBIQUITY*
SCALE
SAFETY
(MOBILE)

Continuous Delivery

ContinuousDelivery

ContinuouslyDeliver
Day One Day Two and Beyond

Operations is the Secret Sauce

Continuously Delivered Microservices
15
Loosely coupled service oriented
architecture with bounded contexts
If every service has to be updated in
concert, it’s not loosely coupled!
If you have to know about surrounding
services you don’t have a bounded context.

Without taking steps to ensure fault tolerance, 30
dependencies each with 99.99% uptime would result in 2+
hours downtime/month (99.99%30 = 99.7% uptime = 2+
hours downtime in a month).
http://techblog.netflix.com/2012/02/fault-tolerance-in-high-volume.html

Build Reliable Systems
from
Unreliable Components

Microservices The Old Way
20

Cloud Native is NOT:
• Configuring Infrastructure
• Orchestrating Containers
• Composing Distributed Systems
• Supporting Ad-Hoc General Purpose Automation

https://twitter.com/littleidea/status/626767188653797376

GREAT JOB PROVISIONING SERVERS THIS YEAR!
…said no CIO ever.

And they’re not going to
say that about
containers either…

I’ve built homegrown application platforms twice:
• The first took three years before it saw a production application.
• The second took two years.
• Maybe if I do it just two more times…

I regret to inform you, but…
• You’re not that smart.
• You’re not different.
• You’re not special.

10:1the ratio of app developers to platform developers
at “web scale” companies

10:1this was also true of the two platforms I helped build

UNDIFFERENTIATED
HEAVY 
LIFTING

SIMPLE RULES
COMPLEX BEHAVIOR
EXPLICIT CONTRACTS
COMMODITY COMPONENTS

SIMPLE RULES
COMPLEX BEHAVIOR
EXPLICIT CONTRACTS

SIMPLE RULES
COMPLEX BEHAVIOR
EXPLICIT CONTRACTS
Grab Dirt w/ Pheromone
Build Bridge
Attach to Ant on Edge
1000’s of Ants
Hardwired into Brain
Colonies, Bridges, Rafts

What if our platform
worked this way?

3-5 Different Server Builds
If your software doesn’t fit into one of these,
your software is broken.
Zero Deviation or Customization

PLATFORM
IS
OMAKASE

SPRING BOOT
40
OMAKASE TWELVE FACTOR APPS
http://start.spring.io

SPRING CLOUD
41
http://cloud.spring.io
https://network.pivotal.io/products/p-spring-cloud-services
OMAKASE DISTRIBUTED SYSTEMS

SPRING XD
42
OMAKASE BATCH AND STREAM DATA PROCESSING
http://projects.spring.io/spring-xd

http://spring.io/platform

PIVOTAL CLOUD FOUNDRY - OMAKASE RUNTIME PLATFORM

If your software doesn’t fit into this
platform, then your software is
probably broken.

Polyglot
Programming?

SIMPLE RULES
COMPLEX BEHAVIOR
EXPLICIT CONTRACTS

Simple Rules
• Boot Property Resolution
• Boot Config Precedence
• Circuit Breaker FSM
• Eureka Cache Server Resolution
• Buildpack Detect/Compile/
Upload
• Java BP Memory Heuristic
• LRP/Task Lifecycle
• Desired/Actual State
Convergence
• STDOUT/ERR Log Aggregation
• Routing Table Maintenance

CONTRACTS

Commodity Components?
50
THOUSANDS
OF
MICROSERVICES!

So what does a platform like this of allow you to do?

#1: Get your head around Conway’s Law.
52
Any organization that designs a system (defined broadly) will
produce a design whose structure is a copy of the organization's
communication structure.
Melvyn Conway, 1967

#2: Invoke the Inverse Conway Maneuver

#3: Start Delivering Business Capabilities
54
Product
Mgr
UX Dev QA DBA
Sys
Admin
Net
Admin
Storage
Admin
BUSINESS CAPABILITY TEAMS
BUILDING MICROSERVICES
PLATFORM OPERATIONS TEAM
Adapted from: http://www.slideshare.net/adriancockcroft/goto-berlin
Self
Service
API

But what if I don’t have a platform like this?
• Probably going to make some things too complicated/hard…
• Probably going to need specialization at multiple levels of your
architecture…
• Probably going to stay stuck in or rebuild your silos…

We need the platform to remind us:
• We’re not that smart.
• We’re not different.
• We’re not special.

So we can get back to why we’re here…
57

Game On
http://pivotal.io/cloud-native

The Cloud Native Journey

More Related Content

What's hot

Viewers also liked

Similar to The Cloud Native Journey

More from Matt Stine

Recently uploaded

The Cloud Native Journey