EMC World 2016 - code.07 Resiliency and Availability of a Cloud Native Infrastructure

1© Copyright 2016 EMC Corporation. All rights reserved. 1© Copyright 2016 EMC Corporation. All rights reserved.

RESILIENCY AND AVAILABILITY OF A CLOUD NATIVE INFRASTRUCTUREJONAS ROSLAND, EMC {code}DEVELOPER ADVOCATE & COMMUNITY MANAGER

4© Copyright 2016 EMC Corporation. All rights reserved.

• High Availability solutions• Mostly Primary-Secondary, Master-Slave• Provides redundancy

FIRST, SOME HISTORY


• Resiliency is a quality in objects to hold or recover their shape• Example: If you bend a spoon and it bends right back

— that's resiliency

SO WHAT IS RESILIENCY?


• Create services that withstand pressure• Foster a modern mindset in operations• Treat failures as normal occurrences, not fires

HOW DOES SPOON BENDING APPLY TO IT?


• Service failures are treated as non-critical issues• Applications and services self-heal• The infrastructure supports this with modern tools

FAILURE HANDLING


• Focused but not necessarily fully dedicated• Not limited to a single master-slave relationship

• Example 1: 20 nodes with resources to run services such as Hadoop, web servers and databases• Example 2: VMware clusters

MODERN INFRASTRUCTURE


• Not just server-side clustering tools• Many layers• Schedulers, service discovery, logging, monitoring

and much more

MANAGING THIS INFRASTRUCTURE


• Collection of compute resources• Spread out horizontally• Brings scale to your

deployments– Docker Swarm– Mesos– Kubernetes– Cloud Foundry

RESOURCE MANAGERS AND SCHEDULERS


EXAMPLE


• Enables apps and infrato automatically findparts of each other– Consul– etcd– SkyDNS– Zookeeper

SERVICE DISCOVERY


EXAMPLE Service Discovery

Java App

2.3.4.5:8080 Where isJava App?2.3.4.5:8080


EXAMPLE Service Discovery

Java A

pp

3.4.5.6:9090Where is

Java App?3.4.5.6:9090


• All logs in one place

• Everything searchable

LOGGING


EXAMPLE


• Sensu• Datadog• Prometheus• New Relic• Ruxit

MONITORING AND ANALYTICS


EXAMPLE


• Everything is managed through smart tools• The tools have integrations to understand hardware• By changing the processes you’re more prepared• Being more prepared is crucial to deal with failures

when they happen

And they will happen

LOOK OF PHYSICAL INFRASTRUCTURE


But what about mysuper special app?


Applications haveto store data, right?


• Storing data (state) is a critical component of any application• Where they store this state defines their class

– Connected database– In memory– Local disk

APPLICATION STATE DIFFERENCES


• Store no critical data locally• Can be scaled as needed• Recovers quickly

STATELESS APPLICATIONS


• Services that store state• Have usually been treated as HA apps• Can be scale-out or scale-up

STATEFUL SERVICES


APPLICATIONS BUILT FROM SERVICESFront End or Non-Persistent

Data Services (Persistent)

Scal

e-Up

Scale-Out

CassandraPostgresRedis CouchDB

Elastic SearchHadoop

MariaDB

Mysql

Nginx

HAProxy

MongoDB

RabbitMQTomcat

Memcached

ScaleIO ECS

ApacheRails

Language Specific HTTP


Demo of resiliency


• Several applications, stateful and stateless, are running and working together• Cascading server failures occurs• Applications are restarted and automatically heal

themselves• The servers are back online and automatically join

the cluster of resources again

DEMO OF FAILURE HAPPENING


• Being prepared is crucial, surprises shouldn’t happen• Use smart tools to deal with issue quickly• Leverage smart infrastructure that allows your apps

to self-heal• Manage your datacenter as an entity, not silos

SUMMARY


Before opening up for questions


• Hands-on lab with Docker, Mesos and REX-Ray• Free stickers at our booth• Join our community at community.emccode.com• See all our projects at emccode.com• And follow us on Twitter @EMCcode

CONTINUE THE DISCUSSION


@EMCcode@jonasrosland

emccode.comcommunity.emccode.com

Come visit us at Booth #1044 or in the vLab

Questions?


Technology

EMC World 2016 - code.07 Resiliency and Availability of a Cloud Native Infrastructure