Cloudify Your Business

CLOUDIFY YOUR BUSINESS

Wayne wallscloud evangelist

Wednesday, August 21, 13


3

Self-Service


4

On-Demand


5

Metered


6

Resource Pooling


7

Broad Network Access


NIST SAys...

8


NIST says...

9


NIST says...

10


11


12

Financial Services Data Analysis & ForecastingMapReduce Data AnalyticsDistributed, Web 2.0 Apps

REVOLUTIONARY


13

SAPPeopleSoftSharePointSQLHome GrownClient-Server Based

EVOLUTIONARY


14

Big Promise of Cloud


15

Scale!


16

High-Availability vs Service Resiliency


17

What is HA?

Active/PassiveActive/Active


18

:Problem:Single Point of Failure


19

:Solution:MAKE TWO OF ‘EM!


20

Hammer & Nail Solution


21

High-Availability has Problems


22

Fails In Terrible Ways &Doesn’t Really Scale


23

Two Options to “HA”


24

Take a non-distributed system and drop HA on top of it

Option #1


25

NFS


26

Mean Time Between Failures (MTBF)


27


28

Mean Time To Recovery (MTTR)


29

Expected failures of a traditional HA system are catastrophic


29



29


System not designed to be distributed


29




29



Failure forces it to be distributed


29





29




Cannot take distributed failure conditions into account


29






29





Best case scenario: complete failure


30

Take a distributed system and make the right tradeoffs

Option #2


31

Service Resiliency


32

Examples


33

Percona XtraDBCassandra

Riak


34

CephGlusterFS


35

Constant Health Checks


36

What is in a Running Application?


37

Availability vs Reliability


38


38

Reliability is the likelihood that a given component or system will be functioning when needed as measured over a given period of time.


38

Reliability is the likelihood that a given component or system will be functioning when needed as measured over a given period of time.

Availability is the percentage of times that a given system will be functioning as required.


39

Server Service


40

Hardware does not get a pass...


41

Think availability from the service layer(s) perspective


42


43

Apps in a Cloudy World


44

Greenfield vs Legacy


45

Greenfield


45

Greenfield

1. Focus on the service, not the server


45

Greenfield

1. Focus on the service, not the server2. Identify & tear apart stateless and stateful parts of your application


45

Greenfield

1. Focus on the service, not the server2. Identify & tear apart stateless and stateful parts of your application3. Make stateful parts redundant using distributed data stores


45

Greenfield

1. Focus on the service, not the server2. Identify & tear apart stateless and stateful parts of your application3. Make stateful parts redundant using distributed data stores4. Know the dependencies of your system and the impact of failure


45

Greenfield

1. Focus on the service, not the server2. Identify & tear apart stateless and stateful parts of your application3. Make stateful parts redundant using distributed data stores4. Know the dependencies of your system and the impact of failure5. Use micro-services to make dependencies explicit


46

Legacy


46

Legacy

1. Cloud Instances != server


46

Legacy

1. Cloud Instances != server2. Plan to reduce mean time to recovery (MTTR)


46

Legacy

1. Cloud Instances != server2. Plan to reduce mean time to recovery (MTTR)3. "We're HA, we're all good." -> Wrong.


46

Legacy

1. Cloud Instances != server2. Plan to reduce mean time to recovery (MTTR)3. "We're HA, we're all good." -> Wrong.4. Think about stateful vs stateless parts of your application and work piece by piece


46

Legacy

1. Cloud Instances != server2. Plan to reduce mean time to recovery (MTTR)3. "We're HA, we're all good." -> Wrong.4. Think about stateful vs stateless parts of your application and work piece by piece5. Be creative about trade-offs: many apps that run on more than one server have some type of common backend (NFS)


Thank You!


Technology

Cloudify Your Business