Taylor RhodesRackspace

THE RIGHT (AND WRONG) WAY TO SCALE

The Right (And Wrong) Way to ScaleTaylor Rhodes

Changing the way theworld thinks about

SCALING

Zack Rosen Ben Golub Alex PolviCEO, CoreOSCEO, DockerCEO, Pantheon

What's on their minds?

Retired instances

NOISY NEIGHBORS

Multi-tenant Cloud at Scale

BEHAVIOR PERFORMANCE AVAILABILITY

SCALE

TRAFFIC

SMALL LARGE

COMPLEXITY

Complexity = More Cost

OVERPROVISIONING

ARCHITECT FOR

FAILURE

ARCHITECT FOR

INCONSISTENCY

VIRTUALIZATIONTAX

$

PROTOTYPE

GROW

OPTIMIZE

FANTASTIC FOR RUNNING AT

SCALE

COLOFANTASTIC FOR STARTING QUICKLY

MULTI-TENANTCLOUD COLOCATION

simple to scale

elastic

simple to scale

elastic

vs.

The Big Tradeoffs

Scaling OptionsToday

+

MULTI-TENANTCLOUD COLOCATION

simple to scaleelastic

vs.

We all want the same thing

Scaling OptionsToday

+

OnMetal

OnMetal

BARE METAL SERVERS

API-drivenInstantly Available

Highly Specialized

NoHypervisor

OnMetal

OnMetal

API HARDWARE

Simplicity atScale

Performancecost

OnMetal

SolidState

Detached Fans

Low Latency:10-Gigabit Networking

Optimized for Specific Workloads

DATABASESLOW-LATENCY

CACHING

HANDLING WEB

REQUESTS

Sexy Specs

DATABASES

PCIe Flash Storage: 3.2TB

RAM: 128GB

IOPS: more than 200,000

What About Virtualization?

Another Way to Scale?

STAY FAST AND LEAN

Scaling Cloud Apps

Wrong Way•Virtualized •One-size-fits-all servers•Running in shared environments

Right Way•Bare metal servers•Instantly available•API-driven •Highly specialized to the specific job you are doing

Why Rackspace?

•We’re not a hardware company

• But we listen to our customers

•OnMetal is open source and good for everybody

•We’ll differentiate on service

OnMetal

rackspace.com/onmetal

Sign up now for early availabilty

General availabilty: late July

The Right (And Wrong) Way to ScaleTaylor Rhodes