EMC World 2016 - cnaITL.05 Unstructured and Structured PaaS Demystified

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

UNSTRUCTURED AND STRUCTURED PAAS DEMYSTIFIEDJONAS ROSLAND, EMC {CODE}@JONASROSLAND

4© Copyright 2016 EMC Corporation. All rights reserved.

PAAS = CLOUD + MAGIC?


• Clustered servers• Manual deployments• Redundancy, not necessarily high availability

BACK IN THE OLD DAYS


• Infrastructure as a Service• Deploy virtual machines• Manual/half-automated way of deploying apps• Almost efficient

THEN SOME TIME AGO


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

NOW - PLATFORM AS A SERVICE


• Multiple masters• Can span across datacenters and locations• Aggregates resources and roles• Enables use of standardized frameworks

PAAS ARE ALWAYS DISTRIBUTED SYSTEMS


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

and much more

MANAGING THIS INFRASTRUCTURE


• Easy, standardized ways of deploying apps• Platforms made for integration, not silos• Enhanced functionality for managing both modern

and traditional apps

Brings order out of chaos

THE END RESULT


Standard definitions


PAAS SITS ON TOP OF SCHEDULERS


• Manages all physical/virtualresources• Deploys and schedules apps• Handles hardware failures

RESOURCE MANAGERS AND SCHEDULERS


SCHEDULING


• Enables apps and infrato automatically findparts of each other• Keeps track of how to

connect and use theapplication services

SERVICE DISCOVERY


SERVICE DISCOVERY

Java App

2.3.4.5:8080 Where isJava App?2.3.4.5:8080


APPLICATIONS RUN IN CONTAINERS

Code Code andrequirements Container


• 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


OPERATING AN APPLICATION PLATFORM

Custom Container Platform

Container Platforms

Cloud-Native Platform

BUILD YOUR OWN PACKAGED BUT COMPOSEABLE PACKAGED


PLATFORMS ENABLING SIMILAR FEATURES

• Supports microservices and loosely coupled services• Scales out quickly• Abstracts away virtual and physical resources• Infrastructure as Code friendly


DIFFERENCES IN PLATFORMS

• Run cloud native applications• Structured/Packaged• Pre-determined architecture and

capabilities• Focused and opinionated• Operated by major releases

• Run any application• Unstructured/Composable• Build it yourself• Move as fast as you want• Readily adopt new features

Container Platforms Cloud Native Platforms


• Cloud Native platforms looks at your code, downloads the requirements and builds a new container to run your apps• Container Platforms takes already bundled containers

and runs them• This changes the way you would handle a CI/CD

scenario depending on the type of platform you use

DIFFERENCES IN CONTAINERS


CLOUD NATIVE PLATFORM

Write codePush it

Platform gathersrequirements

Builds container

Container is deployed


CONTAINER PLATFORM – METHOD ONE

Write codePush it


Gather requirementsBuild container


CONTAINER PLATFORM – METHOD TWO

Downloadcontainer

Containerregistry

Request torun app



CLOUD FOUNDRY - PACKAGED

}Packaged


MESOS - COMPOSED


COMPOSED AND PACKAGED

Mesos

Marathon Deis Cloud Foundry Chronos


• Completely depends on your needs• Both methods are valid for different purposes• You can run multiple environments, at the same

time, no need to lock yourself into just one

SO WHICH ONE SHOULD YOU CHOOSE?


• When the platform will be your differentiator• When you have highly skilled developers and

operations• When you want to participate in building the tools,

skills and software to run it• When you have enthusiastic employees eager to

learn and support new systems

CHOOSE UNSTRUCTURED/COMPOSABLE


• When your applications are the differentiators• When you have highly skilled developers• When you want to provide a stable and proven

platform

CHOOSE STRUCTURED/PACKAGED


• PaaS is not magic• Container technology is the central theme• Unstructured/structured can be better described as

composed/packaged• Using both is absolutely valid!

SUMMARY


Before opening up for questions


Data Persistence in the New Container WorldWednesday 3PM

Joshua BernsteinVP of Technology for ETD

Tobi Knaup CTO & Co-Founder of Mesosphere

Guru Session


@EMCcode@jonasrosland

emccode.comcommunity.emccode.com

Come visit us at Booth #1044 or in the vLab!

Questions?

EMC World 2016 - cnaITL.05 Unstructured and Structured PaaS Demystified

Technology

Transcript of EMC World 2016 - cnaITL.05 Unstructured and Structured PaaS Demystified